Closed theduke closed 4 days ago
Currently, when running wasmer deploy with an unchanged named package, the CLI will:
wasmer deploy
If the package already has a version matching the package hash, the "ask to bump" step should be skipped, and the matching version should be used.
There should potentially be a warning/confirm step if the version number in wasmer.toml does not match the auto-determined version.
Relevant backend query:
{ getPackageVersionByHash () }
Currently, when running
wasmer deploy
with an unchanged named package, the CLI will:If the package already has a version matching the package hash, the "ask to bump" step should be skipped, and the matching version should be used.
There should potentially be a warning/confirm step if the version number in wasmer.toml does not match the auto-determined version.