Suggestion: also support README_API_KEY in addition to RDME_API_KEY

[nickcampbell18]

Hi folks 👋

We recently switched from using the GitHub action to a shell script, because we wanted some extra automation around the deployment. Locally we use rdme login, but in CI we just use an API key.

Anyway, I exported the environment variable README_API_KEY based on the secret we'd set for the action - ${{ secrets.README_API_KEY }} - but my command failed telling me I needed a --key argument. It was only after re-reading the docs I noticed the subtle difference and I should have used RDME_...!

Do you think it might be worth also checking for README_API_KEY in addition to the existing one? Seems unlikely I would be using README_API_KEY to do something else, so this could be a neat ergonomics improvement IMO.

[kanadgupta]

Hey @nickcampbell18 — definitely agreed here. Will make sure this enhancement is included in v9!

[kanadgupta]

@nickcampbell18 this change was added in 9.0.0-next.8. Thanks for writing in about this!

https://github.com/readmeio/rdme/releases/tag/9.0.0-next.8
https://www.npmjs.com/package/rdme/v/9.0.0-next.8

[kanadgupta]

🎉 This issue has been resolved in version 9.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• v9.0.0
• GitHub release

Your semantic-release bot 📦🚀