This PR updates the CircleCI config to use two distinct npm contexts (read-only and publish). This reduces the risk of accidentally publishing in a step that should not. Additionally, it uses a new automation-type token that allows us to enable 2-Factor Auth for login but not for the publishing token.
Once I transition our projects, I will delete the old npm context.
https://app.shortcut.com/homebound-team/story/13496/regenerate-ci-npm-tokens
This PR updates the CircleCI config to use two distinct
npmcontexts (read-only and publish). This reduces the risk of accidentally publishing in a step that should not. Additionally, it uses a new automation-type token that allows us to enable 2-Factor Auth for login but not for the publishing token.Once I transition our projects, I will delete the old
npmcontext.