feat(sentry): use correct env

[jog1t]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[jog1t]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• fix: add missing workflow fucntionality for queues #4165
• chore(frontend): add default vite sentry url #4163
• chore: update exmaples #4162
• fix(rivetkit): remove top-level promise errors #4161
• fix: clean up vite hacks #4160
• feat(workflow): connect workflow visualizer with live data #4153
• feat(sentry): use correct env #4149 👈 (View in Graphite)
• fix: rivetkit build #4147
• feat(dashboard): workflows ui #4081
• feat(dashboard): traces timeline ui #4056 : 1 other dependent PR (#4100 )
• fix(traces): separate entrypoints #4119 : 1 other dependent PR (#4126 )
• refactor(rivetkit): migrate granularly to zod v4 #4121
• fix(rivekit): stub traces in browser #4120
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

Code Review - PR #4149: feat(sentry): use correct env

Summary

This PR adds support for configuring the Sentry environment via VITE_APP_SENTRY_ENV to properly distinguish between staging and production deployments in Sentry.

Issues Found

🐛 Critical Bug: Missing Import in frontend/packages/components/src/third-party-providers.tsx

Location: frontend/packages/components/src/third-party-providers.tsx:39

The file uses commonEnv() on line 39 but doesn't import it. This will cause a runtime error.

// Line 39 - uses commonEnv() but it's not imported
environment: commonEnv().VITE_APP_SENTRY_ENV,

Fix needed: Add the import at the top of the file:

import { commonEnv } from '@/lib/env';

Note: The frontend/src/components/third-party-providers.tsx file correctly imports commonEnv, but the packages version does not.

---

⚠️ Code Quality: Duplicate tunnel Configuration

Location: frontend/packages/components/src/third-party-providers.tsx:36-38

The diff shows a duplicate tunnel assignment was removed, which is good. However, verify that the remaining tunnel configuration is correct:

// Before (had duplicate):
tunnel: getConfig().sentry?.tunnel,
tunnel: __APP_TYPE__ === "cloud" ? cloudEnv().VITE_APP_SENTRY_TUNNEL_URL : undefined,

// After (only one remains):
tunnel: getConfig().sentry?.tunnel,

Make sure this change doesn't break cloud-specific tunnel configuration if it was intentional.

---

Positive Changes

✅ Proper Environment Separation: Using VITE_APP_SENTRY_ENV allows proper environment tagging in Sentry
✅ Docker Configuration: Correctly uses RAILWAY_ENVIRONMENT_NAME with fallback to staging
✅ Schema Validation: Added to commonEnvSchema with proper optional typing
✅ Debug Logging: Console log in vite config helps understand Sentry plugin state

Recommendations

1. Fix the import - Add commonEnv import to frontend/packages/components/src/third-party-providers.tsx
2. Verify tunnel configuration - Confirm that removing the cloud-specific tunnel logic is intentional
3. Consider default value - The schema marks VITE_APP_SENTRY_ENV as optional. Consider if a default value (like 'development') would be appropriate when not set
4. Test both builds - Verify both the main frontend and the components package build correctly with these changes

Test Coverage

No new tests were added. Consider adding tests for:

• Sentry initialization with the new environment parameter
• Proper environment value propagation from env vars

---

Action Required: Fix the missing import before merging to prevent runtime errors.

[graphite-app]

Graphite Automations

"Test" took an action on this PR • (02/06/26)

1 assignee was added to this PR based on Kacper Wojciechowski's automation.

[graphite-app]

Merge activity

• Feb 10, 8:45 AM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Feb 10, 8:46 AM UTC: CI is running for this pull request on a draft pull request (#4166) due to your merge queue CI optimization settings.
• Feb 10, 8:48 AM UTC: The Graphite merge queue removed this pull request due to downstack failures on PR #4081.
• Feb 10, 7:35 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Feb 10, 7:36 PM UTC: CI is running for this pull request on a draft pull request (#4167) due to your merge queue CI optimization settings.
• Feb 10, 7:36 PM UTC: Merged by the Graphite merge queue via draft PR: #4167.