Releases: oxc-project/setup-rust
Releases · oxc-project/setup-rust
v.1.0.16
v1.0.15
Immutable
release. Only release title and notes can be modified.
fix: use cache-directories instead of workspaces for absolute target-dir rust-cache's `workspaces` input uses `path.join(root, target)` which on Windows concatenates the workspace root with an absolute path on a different drive, producing invalid paths like `D:\a\repo\E:\target`. Instead of passing target-dir via workspaces: - Set `cache-targets: false` when target-dir is set (no ./target exists) - Set `cache-directories` to the target dir (adds paths directly without path.join) - Revert to upstream Swatinem/rust-cache (no fork needed) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
v1.0.14
Immutable
release. Only release title and notes can be modified.
feat: add `target-dir` input for custom cargo target directory (#39) Adds support for redirecting compilation artifacts to a custom directory (e.g., a Dev Drive on Windows) by setting `CARGO_TARGET_DIR` and configuring rust-cache's `workspaces` accordingly to avoid cache misses. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
v1.0.13
v1.0.12
v1.0.11
v1.0.10
v1.0.9
v1.0.8
What's Changed
- chore(deps): update taiki-e/install-action action to v2.62.16 by @renovate[bot] in #22
- chore(deps): update taiki-e/install-action action to v2.62.33 by @renovate[bot] in #23
- chore(deps): update taiki-e/install-action action to v2.62.37 by @renovate[bot] in #24
- chore(deps): update taiki-e/install-action action to v2.62.41 by @renovate[bot] in #25
Full Changelog: v1.0.7...v1.0.8
v1.0.7
Only save Valgrind cache on main branch Split the Valgrind cache step into two separate steps: - Save and restore on main branch - Restore only on PR branches This prevents cache pollution from PR branches while still allowing PRs to benefit from the cached Valgrind installation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>