docs(remix): Sync Remix 3 page with SDK 11.5.0

[sentry-junior]

sentry-remix-v3-upload-sourcemaps now also reads the project from SENTRY_PROJECT, so --project is no longer the only option (getsentry/sentry-javascript#25079).

via Charly Gomez.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Oct 7, 2026 2:58pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Oct 7, 2026 2:58pm UTC

[github-actions]

Please update the IS YOUR CHANGE URGENT? section of the PR description:

• Select exactly one option.
• If you selected an urgent or other deadline, provide the date as YYYY-MM-DD.

This information helps the Docs team prioritize your review.

[cursor]

The source-maps upload docs now say a project may come from an environment variable. The plan checks page loads, client errors, and pageload time on that page. An issue escalates when client errors rise or that page stops loading.

Monitoring in production

Services: sentry-docs.

Mention @change-monitor in a comment to update the plan.

Plan

What changed

Visitors to the Remix 3 guide now read that sentry-remix-v3-upload-sourcemaps takes the project from SENTRY_PROJECT or from --project. The old text said --project had to be passed.

sentry-docs must deploy before this wording is live. The change is one MDX sentence. It does not ship develop-docs.

Risk

A failed static build can drop this page. Readers then hit a missing Remix 3 guide. Traffic is low, about ten loads in seven days. Wrong wording can send alpha users to a failed source-map upload. The blast is this page on the shared docs catch-all route.

Intended effect

This is a docs wording change. Telemetry cannot show the new sentence. Leave intended_effect unknown unless a person reads the live page.

confirmed means the Remix 3 page says a project is required from --project or SENTRY_PROJECT. absent means the page still says --project has to be passed. There is no metric for that text.

Regression watch

A bad MDX render can 404 this page or throw in the browser. Watch client errors and page loads on this path. Do not treat a single quiet day as a missing page. Traffic is sparse.

Signal	Baseline	Band	Window	Rule	Source
Remix 3 client errors	0 events, 0% of 1 load	0-0 events per 24h	2026-10-06T14:56:00Z to 2026-10-07T14:56:00Z	Hold at zero. Detected if the 24h count rises above 0.	Sentry org sentry project docs. Query environment:production http.url:*/platforms/javascript/guides/remix/remix-3* with count().
Remix 3 client errors (7d)	1 event, 10% of 10 loads	0-1 events per 7d	2026-09-30T14:56:00Z to 2026-10-07T14:56:00Z	Hold at 0-1. Detected if the 7d count rises above 1 or a new title appears. The 7d event title was Event: Event \Event` (type=error) captured as promise rejection`.	Same project and query, period 7d, group by title.
Remix 3 page loads	1 per 24h, 10 per 7d	0-3 loads per 24h	24h: 2026-10-06T14:56:00Z to 2026-10-07T14:56:00Z. 7d: 2026-09-30T14:56:00Z to 2026-10-07T14:56:00Z	Hold near 1.4 loads per day. A 24h zero can be noise. Detected if a later 7d total falls below 5.	Sentry org sentry project docs. Metric docs.page.load with path:"/platforms/javascript/guides/remix/remix-3/", sum(value).

If errors rise, inspect client exceptions on that URL. If page loads fall over seven days, check whether the Remix 3 path still exists in the static build.

Not observable

The live sentence that names SENTRY_PROJECT is not in telemetry. Pageload time is too sparse for a band: 3 sampled pageload or navigation spans in 7d, p95 482ms, traces sample rate 0.3. Server http.server spans for this path were 0 over 7d because pages are static. docs.page.not_found stores only the first two path segments, so it cannot name remix-3.

[cursor]

Verified in production

• The live Remix 3 guide still shows the new SENTRY_PROJECT wording, with no client errors.
• The live Remix 3 guide still shows the new SENTRY_PROJECT wording, with no client errors.