Skip to content

Commit d3ff875

Browse files
chargomeclaude
andcommitted
docs(nextjs): Simplify the changelog entry
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1 parent 43bbfa7 commit d3ff875

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎CHANGELOG.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
- **feat(nextjs): Never emit trace meta tags from a prerender ([#25141](https://github.com/getsentry/sentry-javascript/pull/25141))**
88

9-
Apps with `cacheComponents` enabled get the `sentry-trace` and `baggage` meta tags again, so a pageload joins the trace of the server request that rendered the page. The server SDK no longer writes these tags while Next.js prerenders a page, so a cached shell never carries the trace of another visitor. This also covers ISR pages. Apps that set up OpenTelemetry themselves register `NextSentryPropagator` instead of `SentryPropagator` and call `markPrerendersOnTracerProvider` with their tracer provider to get the same behaviour.
9+
Pageloads of apps with `cacheComponents` enabled are connected to their server request again. Pages that Next.js prerenders no longer carry trace information, so a cached page can no longer connect visitors to a request that was not theirs. This also applies to ISR pages.
1010

1111
Work in this release was contributed by @Philip-Nwabuwa and @4ktLuffy. Thank you for your contributions!
1212

0 commit comments

Comments
 (0)