ci: clear cargo registry cache before workspace publish dry-run #2530
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
The workspace publish dry-run fails with `unresolved import
miden_utils_sync::OnceLockCompat` during verification. This happens
because cached registry data from previous CI runs can interfere with
cargo's temp registry used for workspace dependency resolution.
During verification, cargo should use the packaged v0.21.0 from the
temp registry, but stale cache entries may cause it to resolve
against crates.io data instead (where v0.20.1 lacks OnceLockCompat).
Clear ~/.cargo/registry/{cache,index,src} before the dry-run to ensure
fresh resolution without interference from cached data.
Closes #2505
huitseeker
added
the
no changelog
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.
The workspace publish dry-run fails with
unresolved import miden_utils_sync::OnceLockCompatduring verification. This happens because cached registry data from previous CI runs can interfere with cargo's temp registry used for workspace dependency resolution.During verification, cargo should use the packaged v0.21.0 from the temp registry, but stale cache entries may cause it to resolve against crates.io data instead (where v0.20.1 lacks
OnceLockCompat).=> Clear
~/.cargo/registry/{cache,index,src}before the dry-run to ensure fresh resolution without interference from cached data.Replaces #2505