Conversation
|
Do we have documentation detailing the need for the NPM_TOKEN and it's 90 days rotation somewhere? |
Contributor
Author
Not yet. This is a newly discovered issue. |
danebenal
approved these changes
Feb 25, 2026
rustyjux
approved these changes
Feb 25, 2026
Contributor
rustyjux
left a comment
rustyjux
left a comment
There was a problem hiding this comment.
Good catch. Thanks for laying it out clearly in the chat message.
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
3 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.
Fixes 403 Forbidden on Cypress tests.
The 403 Forbidden happens when the npm registry rate-limits unauthenticated requests. In our workflow, several images run npm install in parallel (cypress-jwks-url, feeder, apsportal, cypress, etc.), so the runner hits that limit and npm returns 403.