ci: Move the DSN for the jest project to github secrets#116776
Merged
Conversation
Some external folks are sending data into our project. its not a huge problem because we have special envs that let us filter out the random stuff. but someone could easily r-euse our envs and then we would be in trouble. the value is already in github here: https://github.com/getsentry/sentry/settings/secrets/actions
github-actions
Bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9670c23. Configure here.
joshuarli
approved these changes
Jun 3, 2026
Pass the SENTRY_JEST_DSN secret as SENTRY_DSN env var so the jest balancer job can report to Sentry, matching the frontend workflow. Co-Authored-By: Claude Opus 4.6 <noreply@example.com>
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.
Some external folks are sending data into our project. its not a huge problem because we have special envs that let us filter out the random stuff. but someone could easily r-euse our envs and then we would be in trouble.
The new DSN is configured in sentry already: https://sentry.sentry.io/settings/projects/jest/keys/232ba39ed1567f1852c02e79600c3779/
The value is in github here: https://github.com/getsentry/sentry/settings/secrets/actions.
After this lands, maybe a few days later, we can disable or revoke the old key.