Skip to content

[skill-drift] update(sentry-cloudflare-sdk): document dataCollection option#148

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
skill-drift/sentry-cloudflare-sdk-skill-drift-update-sentry-cloudflare-sdk-1780325400
Open

[skill-drift] update(sentry-cloudflare-sdk): document dataCollection option#148
github-actions[bot] wants to merge 1 commit into
mainfrom
skill-drift/sentry-cloudflare-sdk-skill-drift-update-sentry-cloudflare-sdk-1780325400

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Jun 1, 2026

Warning

Auto-generated from external SDK content. Review all links and code suggestions before acting on them.

Summary

Updates the Cloudflare SDK skill to document the new dataCollection option introduced in v10.54.0 (PR #21237), which provides granular control over captured data and replaces the legacy sendDefaultPii boolean.

Changes

Main Skill (SKILL.md)

  • Updated code examples to use dataCollection.cookies instead of sendDefaultPii
  • Added new "Data Collection Reference" section documenting all dataCollection options
  • Updated config reference table with dataCollection entry and marked sendDefaultPii as legacy
  • Added migration guidance from sendDefaultPii to dataCollection
  • Documented Cloudflare-specific behavior: cookies are OFF by default (unlike other SDKs)

Error Monitoring Reference (error-monitoring.md)

  • Updated all code examples to use dataCollection.cookies
  • Revised PII note to reference dataCollection options
  • Updated best practices to recommend dataCollection configuration
  • Updated troubleshooting table entry for missing request data

Durable Objects Reference (durable-objects.md)

  • Updated code example to use dataCollection.cookies

Key Points

  • No breaking changes: sendDefaultPii still works as a transitional option
  • Cloudflare-specific default: Cookies remain OFF by default to preserve historical behavior
  • Available in: v10.54.0+ (skill already references v10.55.0)
  • Future deprecation: sendDefaultPii will be removed in v11

Reviewed PRs

  • #21237 - feat(cloudflare): Migrate to dataCollection

Source PRs

…option

Automated drift-fix run.

Co-Authored-By: Claude (claude-sonnet-4-5) <noreply@anthropic.com>
Comment on lines +527 to +530
| Old (legacy) | New (v10.54.0+) |
|--------------|-----------------|
| `sendDefaultPii: true` | `dataCollection: { cookies: true }` |
| `sendDefaultPii: false` | `dataCollection: { cookies: false }` (Cloudflare default) |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The documentation suggests an invalid configuration dataCollection: { cookies: false } for disabling cookies. The correct value should be an object like { mode: "off" }.
Severity: MEDIUM

Suggested Fix

Update the migration table to show the correct configuration for disabling cookies. Replace dataCollection: { cookies: false } with dataCollection: { cookies: { mode: "off" } }. Alternatively, clarify that omitting the cookies field also disables cookie collection by default.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: skills/sentry-cloudflare-sdk/SKILL.md#L527-L530

Potential issue: The migration table in the documentation incorrectly advises users to
migrate from `sendDefaultPii: false` to `dataCollection: { cookies: false }`. According
to official Sentry SDK documentation, the `cookies` option does not accept a raw boolean
`false` value. The correct way to disable cookie collection is by using an object with a
mode, such as `{ mode: "off" }`. Users following the current documentation might
encounter TypeScript errors, runtime validation errors, or a silent misconfiguration
where their settings are ignored, potentially leading to unintended data collection.

Did we get this right? 👍 / 👎 to inform future reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants