According to the doc, tokens for custom registries may be specified with environment variables of the form CARGOREGISTRIES_TOKEN where is the name of the registry in all capital letters. But it appears that at the moment while handling the env variable the registry name is not being put in uppercase, meaning if the custom registry name is foo release-plz will try to fetch the corresponding token by CARGO_REGISTRIES_foo_TOKEN key, not CARGO_REGISTRIES_FOO_TOKEN
Would you like to work on a fix? [y]
To Reproduce
Call release-plz release --registry foo against custom registry while having CARGO_REGISTRIES_FOO_TOKEN env variable set.
Bug description
According to the doc, tokens for custom registries may be specified with environment variables of the form CARGOREGISTRIES_TOKEN where is the name of the registry in all capital letters. But it appears that at the moment while handling the env variable the registry name is not being put in uppercase, meaning if the custom registry name is
foorelease-plz will try to fetch the corresponding token byCARGO_REGISTRIES_foo_TOKENkey, notCARGO_REGISTRIES_FOO_TOKENTo Reproduce
Call
release-plz release --registry fooagainst custom registry while havingCARGO_REGISTRIES_FOO_TOKENenv variable set.Expected behavior
Screenshots
Environment
Additional context