fix: pass Sentry auth token for sourcemaps#36
Draft
cursor[bot] wants to merge 1 commit intomainfrom
Draft
Conversation
Sentry's current Next.js sourcemap upload flow expects the auth token\nto be wired through withSentryConfig during production builds.\n\nProvide process.env.SENTRY_AUTH_TOKEN explicitly so build-time\nsourcemap upload can authenticate consistently instead of depending 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.
|
7 tasks
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.
organdprojectbut never passedauthToken, while the current Sentry Next.js sourcemap upload flow expectsSENTRY_AUTH_TOKENto be wired throughwithSentryConfig(...)for production builds.authTokenwiring since the original setup, and the issue resurfaced on recent preview releases as asourcemap_configuration/js_no_sourcewarning.process.env.SENTRY_AUTH_TOKENexplicitly innext.config.tsso build-time sourcemap uploads can authenticate consistently.Type of Change
Sentry Context
releaseis null on the warning events)Verification
pnpm check-types✅pnpm lint.claude/skills; no new lint finding was introduced innext.config.tsChecklist
pnpm check-types)pnpm lint)