chore: add lockfile for Cargo #108
Merged
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 guidance on lock files was recently changed: https://blog.rust-lang.org/2023/08/29/committing-lockfiles.html This makes it easier for downstream distributors to know which exact dependencies work with the release.
|
Thanks. |
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 guidance on lock files was recently changed:
https://blog.rust-lang.org/2023/08/29/committing-lockfiles.html
This makes it easier for downstream distributors to know which exact dependencies work with the release.
For motivation and how I got here: python-calamine is packaged in NixOS and there a lockfile is added to the repository to pin the dependencies. Imho this pinning makes more sense closer to the source rather than on the distribution level.