Update the Juvix lock file when the Package file changes #2522
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.
Adds a new version of the lock file that stores the hash (sha256 digest) of the package file (Package.juvix, juvix.yaml) it was generated from as a field:
The lock file is regenerated when the hash of the package file doesn't match the value of the
checksum
field, i.e when the user updates the package file.Existing lock files are automatically migrated to version 2.