feat: add caching for cargo-release installation #224
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Cache cargo registry and tools directory - Check if cargo-release is already installed before installing - Significantly speeds up release workflow (no more 3+ minute installs) - Uses cache key based on Cargo.lock hash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds caching for cargo-release to speed up the release workflow significantly.
Problem
Every release workflow run takes 3+ minutes just to install cargo-release from source.
Solution
Benefits
Cache Details
Caches:
~/.cargo/bin/- Installed tools including cargo-release~/.cargo/registry/- Downloaded crates~/.cargo/git/db/- Git dependenciesCache key:
${{ runner.os }}-cargo-tools-${{ hashFiles('**/Cargo.lock') }}This will make the release workflow much faster!