You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After compiling the project the following juvix.lock.yaml is generated:
# This file was autogenerated by Juvix version 0.5.2.# Do not edit this file manually.dependencies:
- path: .juvix-build/stdlibdependencies: []
- git:
name: testref: a94c61749678ff57556ee6e4cb1f8fbbddbc4ab1url: https://github.com/anoma/juvix-testdependencies:
- git:
name: stdlibref: 4facf14d9b2d06b81ce1be1882aa9050f768cb45url: https://github.com/anoma/juvix-stdlibdependencies: []
The v0.6.0 tag has been dereferenced to the git hash of the corresponding commit. If you now update the project file to point to a new version of juvix-test and rebuild the project, the v0.6.0 code is still used because the lock file has not changed.
The proposal in this issue is to detect when the project file dependencies and the lock file are not in sync and regenerate the lock file using the new information.
The text was updated successfully, but these errors were encountered:
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:
```
# This file was autogenerated by Juvix version 0.5.4.
# Do not edit this file manually.
version: 2
checksum: d05940a4d3dc0e15451d02e1294819c875ba486ee54e26865ba8d190ac7c27c3
dependencies:
- git:
name: stdlib
ref: f68b0614ad695eaa13ead42f3466e0a78219f826
url: https://github.com/anoma/juvix-stdlib.git
dependencies: []
```
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.
* Closes#2464
Say you have the following project:
After compiling the project the following juvix.lock.yaml is generated:
The
v0.6.0
tag has been dereferenced to the git hash of the corresponding commit. If you now update the project file to point to a new version ofjuvix-test
and rebuild the project, thev0.6.0
code is still used because the lock file has not changed.The proposal in this issue is to detect when the project file dependencies and the lock file are not in sync and regenerate the lock file using the new information.
The text was updated successfully, but these errors were encountered: