Unable to Publish Package with WASMER_TOKEN env var

[ayys]

Describe the bug

I encountered an issue while trying to publish a package to the Wasmer Registry using the wasmer publish command from the CI.

wasmer 4.0.0-beta.2 (18ab43b 2023-06-09)
binary: wasmer-cli
commit-hash: 18ab43bc60d4427676fb2adcee78ef016321b829
commit-date: 2023-06-09
host: aarch64-apple-darwin
compiler: singlepass,cranelift
rustc 1.70.0 (90c541806 2023-05-31)
binary: rustc
commit-hash: 90c541806f23a127002de5b4038be731ba1458ca
commit-date: 2023-05-31
host: aarch64-apple-darwin
release: 1.70.0
LLVM version: 16.0.2

Steps to reproduce

1. Set the registry URL

$ wasmer config set registry.url wasmer.io

2. Export the Wasmer token

$ export WASMER_TOKEN="wap_..."

3. Publish the package

$ wasmer publish
error: cannot publish package: not logged into registry "https://registry.wasmer.io/graphql"

4. Set the registry URL again

$ wasmer config set registry.url wasmer.io
Successfully logged into registry "https://registry.wasmer.io/graphql" as user "..."

5. Retry publishing the package

$ wasmer publish
error: cannot publish package: not logged into registry "https://registry.wasmer.io/graphql"

Expected behavior

I expected the package to publish both times, but it didn't.

Actual behavior

I got an error that I am not logged in to the registry, even though I am.

Additional context

I noticed that WASMER_TOKEN env var does not get added to the global wasmer.toml config file. This could be why I am getting this error.