Repository navigation
fix: bring Cargo.lock to 0.5.6 so locked builds work again - #41
Merged
Merged
Conversation
The 0.5.6 release pull request was merged nine seconds after it was opened, before the release workflow had synced the lock onto it. Cargo.toml says 0.5.6 while Cargo.lock still pinned both crates at 0.5.5, so every `--locked` build has failed since: CI's msrv job, the release build of v0.5.6 and the PKGBUILD.
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
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.
Cargo.toml is at 0.5.6 but Cargo.lock still pins
ravenandraven-guiat 0.5.5. The 0.5.6 release pull request (#39) was merged nine seconds after it was opened, before the release workflow synced the lock onto it.Since then every
--lockedbuild fails with "the lock file needs to be updated": CI's msrv job on main and on every pull request, and the release build of v0.5.6, which is still a draft with no assets.The change is
cargo update --workspace: two version lines, no external dependency touched.cargo metadata --lockedpasses on it.