Describe the bug
Until a month ago, NEAR CLI has used NEAR_ENV when setting the network, like mainnet and testnet.
If folks have differing values on those two environment variables, it will use the old one that's not mentioned in the documentation: https://docs.near.org/tools/near-cli
To Reproduce
See screenshot above
Expected behavior
As a user, if I follow the NEAR CLI documentation, I should be able to correctly target the network of choice and not have confusion.
Or perhaps this is a simple order of operations where the newly declared environment variable (NEAR_NETWORK) takes precedence over NEAR_ENV.
Describe the bug Until a month ago, NEAR CLI has used
NEAR_ENV
when setting the network, likemainnet
andtestnet
. If folks have differing values on those two environment variables, it will use the old one that's not mentioned in the documentation: https://docs.near.org/tools/near-cliTo Reproduce See screenshot above
Expected behavior As a user, if I follow the NEAR CLI documentation, I should be able to correctly target the network of choice and not have confusion.
Or perhaps this is a simple order of operations where the newly declared environment variable (
NEAR_NETWORK
) takes precedence overNEAR_ENV
.