We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wasmer publish
When calling wasmer publish it always defaults to the wapm.io registry, unless a different one is explicitly defined via the --registry flag.
--registry
$ wasmer config set registry.url "https://registry.wapm.dev/graphql" $ wasmer config get registry.url https://registry.wapm.dev/graphql $ wasmer publish # uses the wapm.io registry
wasmer publish should use the registry specified in wasmer config get registry.url
wasmer config get registry.url
It always defaults to wapm.io
$ wasmer -vV wasmer 3.2.0-alpha.1 (45cb9 2023-01-25) binary: wasmer-cli commit-hash: 45cb95c1a83124ea98a0a75e9701962c10d7d7f5 commit-date: 2023-01-25 host: aarch64-apple-darwin compiler: singlepass,cranelift
The text was updated successfully, but these errors were encountered:
wasmer login
I believe this was fixed in #4013.
Sorry, something went wrong.
Michael-F-Bryan
No branches or pull requests
Describe the bug
When calling
wasmer publish
it always defaults to the wapm.io registry, unless a different one is explicitlydefined via the
--registry
flag.Steps to reproduce
Expected behavior
wasmer publish should use the registry specified in
wasmer config get registry.url
Actual behavior
It always defaults to wapm.io
Additional context
The text was updated successfully, but these errors were encountered: