Repository navigation
Cargo.lock: the pins of #166 - #167
Merged
Merged
Conversation
cli#166 moved the rev pins without the lockfile, so release.yml's `cargo build --locked` refused it. Only the git sources move; no crates.io package changes.
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.
#166 moved the rev pins of core, generation, comline-rust and comline-typescript without updating
Cargo.lock. The required test jobs build without--locked, so they passed. release.yml'scargo build --lockedrefused the stale lock on every target.This updates only the lock's git sources to the new pins (resolved with
cargo metadata, nocargo update); no crates.io package changes.