docs(cloudflare): Rework the guide for v11 - #19331
Draft
JPeer264 wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
JPeer264
force-pushed
the
janpeer/sdk-1426-cloudflare-getting-started-manual-setup
branch
from
September 11, 2026 08:45
d9c523d to
1f470d1
Compare
JPeer264
changed the base branch from
master
to
janpeer/sdk-1426-cloudflare-getting-started-manual-setup-v10
September 11, 2026 08:46
JPeer264
added this pull request to stack #19363
September 11, 2026 08:46
JPeer264
force-pushed
the
janpeer/sdk-1426-cloudflare-getting-started-manual-setup
branch
from
September 11, 2026 08:50
1f470d1 to
280d199
Compare
Updates the Cloudflare guide for the APIs v11 removes or changes. Hold until v11 ships; every claim here is wrong on the v10 line. - Remove the `@sentry/cloudflare/nodejs_compat` entrypoint, which no longer exists, from the guide, the Prisma page, the integrations table and the Vercel AI page, and delete its feature page - Drop the `_experimental` Vite plugin options for `buildTimeInstrumentation` and `autoInstrumentation`, both on by default, and remove the experimental alert on the plugin page - Import `wrapRequestHandler` from `@sentry/cloudflare/request`, the only entry that still exports it - Delete the removed `honoIntegration` page - Describe spans as streamed by default on the MCP pages and in troubleshooting, and keep the v10 opt-in as a separate case - Drop the caveat that configured classes must be declared in the Worker entry, fixed by getsentry/sentry-javascript#23282 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
JPeer264
force-pushed
the
janpeer/sdk-1426-cloudflare-getting-started-manual-setup
branch
from
September 11, 2026 09:00
280d199 to
139d9c2
Compare
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
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.
DESCRIBE YOUR PR
closes SDK-1426
Updates the Cloudflare guide for the APIs v11 removes or changes. Hold until
v11 ships; every claim here is wrong on the v10 line.
@sentry/cloudflare/nodejs_compatentrypoint, which no longerexists, from the guide, the Prisma page, the integrations table and the
Vercel AI page, and delete its feature page
_experimentalVite plugin options forbuildTimeInstrumentationand
autoInstrumentation, both on by default, and remove the experimentalalert on the plugin page
wrapRequestHandlerfrom@sentry/cloudflare/request, the onlyentry that still exports it
honoIntegrationpagetroubleshooting, and keep the v10 opt-in as a separate case
entry, fixed by fix(cloudflare): Auto-instrument classes re-exported from the worker entry sentry-javascript#23282
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES