-
Notifications
You must be signed in to change notification settings - Fork 2.4k
differentiate debug/release in cache key #5613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -73,9 +73,9 @@ jobs: | |
| ${{ env.CARGO_HOME }}/registry/cache/ | ||
| ${{ env.CARGO_HOME }}/git/db/ | ||
| target/ | ||
| key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }} | ||
| key: ${{ runner.os }}-cargo-release-${{ hashFiles('**/Cargo.lock') }} | ||
|
||
| restore-keys: | | ||
| ${{ runner.os }}-cargo- | ||
| ${{ runner.os }}-cargo-release- | ||
|
|
||
| - name: Build Release Binary for Smoke Tests | ||
| run: | | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inconsistent cache key naming pattern. This workflow uses
-cargo-release-while other release build workflows (bundle-desktop.yml, bundle-desktop-windows.yml, build-cli.yml) use-cargo-build-release-. Consider using-cargo-build-release-for consistency across all release build workflows.