You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 84f41c3
Browse filesBrowse the repository at this point in the historyBrowse files
fix(nextjs): Apply the prerender trace guard to withSentry on Cloudflare
ISR pages revalidate inside a request of the Worker, where `withSentry` of
`@sentry/nextjs/cloudflare` registers its own tracer provider and propagator.
The guard only covered the setup of the Node SDK, so a shell prerendered in
the Worker got that request's trace. The Next.js integration now marks
prerenders on the tracer provider `@sentry/cloudflare` registered and its
propagator skips a marked context.
Also moves the changelog entry above the contributor line and fixes a test
comment that pointed to a file of the follow-up PR.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,8 @@
4
4
5
5
- "You miss 100 percent of the chances you don't take. — Wayne Gretzky" — Michael Scott
6
6
7
+
- **feat(nextjs)**: Browser pageloads of apps with `cacheComponents` enabled now connect to the server request again. The SDK stopped emitting `sentry-trace` meta tags for these apps because a cached shell could replay the trace of the request that rendered it to every later visitor. The server SDK now refuses to hand out trace context while Next.js prerenders a document, so cached shells never carry a trace, and a tag that is in the document was always rendered for the current request. The guard is part of the tracer provider and propagator the SDK registers, so it does not cover apps that set up OpenTelemetry themselves. This also covers ISR pages, which no longer need the client-side meta tag removal based on `generateStaticParams`; the `isrRoutes` field of the injected route manifest is gone.
8
+
7
9
Work in this release was contributed by @Philip-Nwabuwa. Thank you for your contribution!
8
10
9
11
## 11.6.0
@@ -87,8 +89,6 @@ Work in this release was contributed by @Philip-Nwabuwa. Thank you for your cont
87
89
88
90
Work in this release was contributed by @zkasuran. Thank you for your contribution!
89
91
90
-
- **feat(nextjs)**: Browser pageloads of apps with `cacheComponents` enabled now connect to the server request again. The SDK stopped emitting `sentry-trace` meta tags for these apps because a cached shell could replay the trace of the request that rendered it to every later visitor. The server SDK now refuses to hand out trace context while Next.js prerenders a document, so cached shells never carry a trace, and a tag that is in the document was always rendered for the current request. The guard is part of the tracer provider and propagator the SDK registers, so it does not cover apps that set up OpenTelemetry themselves. This also covers ISR pages, which no longer need the client-side meta tag removal based on `generateStaticParams`; the `isrRoutes` field of the injected route manifest is gone.
0 commit comments