fix: pass Sentry auth token for sourcemaps#37
Draft
cursor[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
Sentry's Next.js sourcemap upload flow expects the auth token to be\nwired through withSentryConfig during production builds.\n\nProvide process.env.SENTRY_AUTH_TOKEN explicitly so build-time\nsourcemap upload can authenticate consistently instead of relying on\nimplicit environment discovery.\n\nFixes WEBVITALS-3P\nCo-Authored-By: Claude <noreply@anthropic.com> Co-authored-by: Sergiy Dybskiy <s@serg.tech>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Description
Fixes a regression in WEBVITALS-3P.
next.config.tsconfigured Sentryorgandprojectbut did not passauthToken, so the Next.js Sentry sourcemap upload step had to rely on implicit environment discovery instead of explicit build auth.c24b9c0, but it never merged intomain, so releases built from the current base still ship without the token wiring.process.env.SENTRY_AUTH_TOKENintowithSentryConfig(...)innext.config.ts.Type of Change
Sentry Context
releaseandenvironmenttags are(null)on the warning events)c24b9c0; issue activity history was not exposed by the available MCP toolsVerification
nodeorpnpmon PATH, sopnpm check-typesandpnpm lintcould not be run here.Checklist
pnpm check-types)pnpm lint)