[wrangler] Disable Sentry error reporting by default#13815
Merged
Conversation
🦋 Changeset detectedLatest commit: b5da47f The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
|
LGTM |
Contributor
|
✅ All changesets look good |
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
The current Sentry consent prompt fires on every error and produces too many false-positive reports. Default WRANGLER_SEND_ERROR_REPORTS to false so we neither prompt nor send by default. Users can still opt in by setting WRANGLER_SEND_ERROR_REPORTS=true.
- Drop the prompt output from the non-interactive 'should not hit sentry after error' snapshot (the consent prompt no longer fires by default). - Remove the two tests that exercised the consent prompt path: that path is no longer reachable because WRANGLER_SEND_ERROR_REPORTS now defaults to false rather than undefined. The remaining tests already cover both the explicit-true and explicit-false env var cases.
d33b3af to
b5da47f
Compare
Contributor
|
Codeowners approval required for this PR:
Show detailed file reviewers |
NuroDev
approved these changes
May 26, 2026
workers-devprod
approved these changes
May 26, 2026
workers-devprod
left a comment
Contributor
There was a problem hiding this comment.
Codeowners reviews satisfied
Merged
penalosa
added a commit
that referenced
this pull request
May 28, 2026
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
3 participants
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.
WRANGLER_SEND_ERROR_REPORTSnow defaults tofalseinstead ofundefined. Previously, when the env var was unset, Wrangler would prompt the user on every error asking whether to report to Sentry. The prompt produces too many false-positive reports, so we now default to off. Users can still opt in by settingWRANGLER_SEND_ERROR_REPORTS=true.A follow-up PR will remove the Sentry codepaths.