chore(ci): add additional test token - #7227
Merged
Merged
Conversation
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This comment has been minimized.
This comment has been minimized.
octavian-snyk
approved these changes
Sep 7, 2026
PeterSchafer
force-pushed
the
chore/add_test_token
branch
from
September 7, 2026 07:27
8ca5bf1 to
9bd7139
Compare
PR Reviewer Guide 🔍
|
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
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Add additional test token
Where should the reviewer start?
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?
Note
Low Risk
Test-only setup change with no impact on CLI runtime or production auth paths.
Overview
Adds
TEST_SNYK_TOKEN_4to theTOKEN_ENV_VARSlist intest/setup.js, so Jest global setup can pick a fourth optional API token when more than one is defined in the environment.Behavior is unchanged otherwise:
selectRandomToken()still chooses randomly among whichever of the listed env vars are set and non-empty, then configures the CLI for integration tests.Reviewed by Cursor Bugbot for commit 9bd7139. Bugbot is set up for automated code reviews on this repo. Configure here.