update Cargo.lock after other hashes #260
Merged
Conversation
This file contains 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
as `update_cargo_lock()` overrides the top level derivations, this will cause hash mismatch errors in the event of other FODs being used in the environment (i.e., `pnpmDeps`) during updates if they also need to be updated
|
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 0add018 |
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.
As
update_cargo_lock()overrides the top level derivations, this will cause hash mismatch errors in the event of other FODs being used in the environment (i.e.,pnpmDeps) during updates if they also need to be updated.gitbutlerin nixpkgs at this revision is a real world example of this occurring, and changing the order of these function calls allows it to run as expected