EXP-2124 Use org secret ADO_NPM_FEED_TOKEN for codat-npm feed auth - #1871
Merged
Conversation
The repo-level NPM_TOKEN secret was backed by a short-lived ADO PAT that expired on 3 Aug, breaking every workflow that runs npm ci. The NPM_TOKEN name is also overloaded across the org (client-sdk-typescript uses it for an npmjs.com publish token), so the ADO feed credential moves to an explicitly named org-level secret shared with the repos that consume the codat-npm feed. Merge after the ADO_NPM_FEED_TOKEN org secret exists; the repo-level NPM_TOKEN secret can then be deleted. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Link check results: |
pmckinney-codat
enabled auto-merge
August 4, 2026 15:16
brucepouncey
approved these changes
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
CI here authenticates to the Azure DevOps
codat-npmfeed using the repo-levelNPM_TOKENsecret, which was backed by a 7-day PAT that expired on 3 Aug — every workflow runningnpm cinow fails withE401.The
NPM_TOKENname is also overloaded across the org:client-sdk-typescriptuses it to mean an npmjs.com publish token. To standardise, the ADO feed credential moves to an explicitly named org-level secret,ADO_NPM_FEED_TOKEN, shared with the repos that consume the feed (this repo and its sibling).What
Renames every
secrets.NPM_TOKENreference (and the matching shell env var) toADO_NPM_FEED_TOKENin the workflows that inject feed credentials into~/.npmrc. No behaviour change otherwise.Merge order
ADO_NPM_FEED_TOKENorg secret exists with repository access including this repo (all consuming repos are public, so visibility must be "selected" or "all" — not "private repositories"). Checks on this PR will stay red until then. After merging, delete the repo-levelNPM_TOKENsecret.Tracked in EXP-2124. Sibling PR: see ticket comments.
🤖 Generated with Claude Code