fix(sentry): Report Vercel environment instead of NODE_ENV - #210
Merged
Merged
Conversation
Preview and production deploys both reported environment=production, mixing preview traffic into production web vitals and errors. Use the Vercel environment so each can be compared on its own (e.g. by Cursor Rollouts, which tracks each environment separately). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sergical
marked this pull request as ready for review
September 29, 2026 19:07
This branch was successfully deployed
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.
Both Sentry configs set
environment: process.env.NODE_ENV, which isproductionon every Vercel build. Preview deploys were therefore reported asproduction, so preview traffic was mixed into production errors and web vitals.This change uses the Vercel environment instead:
NEXT_PUBLIC_VERCEL_ENV, which Vercel exposes to Next.js projects automatically.VERCEL_ENV.NODE_ENV, as before.The
productionname doesn't change, so existing alerts and dashboards filtered onenvironment:productionkeep working. Only preview traffic moves, topreview.This prepares the repo for Cursor Rollouts, which verifies each environment separately against telemetry. It also adds a short Telemetry section to
AGENTS.md, covering the Sentry project, environment and release conventions, and web vitals coverage, so agents know where to look.Web vitals for soft navigations (getsentry/sentry-javascript#23425) are already on by default in
@sentry/nextjs11.0.0 (webVitalsIntegration({ softNavigations: true }), with span streaming as the default), so no SDK config change is needed.Verified with
biome checkandpnpm test:run.