Edge-CLI: deploy command: Pin version of inline packages to strict specific version
Opened this issue · 1 comments
theduke commented
Currently the wasmer deploy command sets the version constraint in app.yaml to the package version, like @1.2.3.
But the version here is actually a semantic version constraint, so if we want to pin the version we need to use an @=1.2.3, at least if the package is in the same directory as the app.yaml, and if the user chooses to deploy a new version of the package when running the command.
Not pinning the version means we do not have a reproducible , fixed deployment.
Note: there is a larger discussion to be had here about lock files and app version pinning, but this is a quick fix that should be sufficient for now.