feat(cli/push): Push with name if available (+ CLI flag) #4912
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.
As of now, while users can push a package to a namespace without a version, they can't attach to it a name as well. This patch introduces the necessary infrastructure for the CLI to be able to push unversioned (as in, named, but without a version) packages to the registry.
For example, if a manifest such as the following
is found in the directory of the package to push, then the result of
wasmer package push
is to push to the registry a package bound to the identifiermy-namespace/my-package
but without a version. This can behaviour can also be enforced with the corresponding--name
flag in thepush
subcommand.This does not allow users to run unversioned packages, as no consensus on naming was reached yet - this means that, as of now, executing
wasmer run my-namespace/my-package:<hash>
will fail. Instead, users can run their package withwasmer run <hash>
.