feat: add Rust build caching to ci-lazer-solana workflow #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: add Rust build caching to ci-lazer-solana workflow
Summary
Adds Rust build caching to the
ci-lazer-solana.ymlGitHub Actions workflow by including thecache-workspacesparameter in the existingactions-rust-lang/setup-rust-toolchain@v1step. This will cache thetarget/directory using theCargo.lockfile hash as the cache key, improving build performance by avoiding recompilation of unchanged dependencies.The implementation follows the same pattern used in other Rust workflows in this repository (
ci-lazer-anchor.yml) and the broader pyth-network organization.Review & Testing Checklist for Human
"lazer/solana -> target"correctly maps to the working directorylazer/solanaand that Rust builds output totarget/in that directoryNotes
actions-rust-lang/setup-rust-toolchain@v1rather than manual cache actionsCargo.lockcontent, ensuring cache invalidation when dependencies changeLink to Devin run: https://app.devin.ai/sessions/9d14059dbcb54ba1b93b7f9481e3e878
Requested by: Jayant ([email protected])