fix: correct CaptureIntegrationSpecificIds.V2 feature flag string#1250
Conversation
…h server The server sends the V2 feature flag as `captureIntegrationSpecificIds.V2` (with a dot), but the SDK was looking up `captureIntegrationSpecificIdsV2` (no dot). This caused the V2 value to silently fall back to 'none', preventing IntegrationCapture from initializing for customers whose legacy V1 flag is set to False. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ests Tests were using the SDK constant value as the flag key, which matched the (incorrect) constant and always passed. Updated all test configs to use the literal server key 'captureIntegrationSpecificIds.V2' so tests will catch key mismatches in the future. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview Updates the Reviewed by Cursor Bugbot for commit cb60633. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit bc1f166. Configure here.
Update the interface property to 'captureIntegrationSpecificIds.V2' so the type definition matches the runtime key shape. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
## [2.64.1](v2.64.0...v2.64.1) (2026-04-16) ### Bug Fixes * correct CaptureIntegrationSpecificIds.V2 feature flag string ([#1250](#1250)) ([50c2e29](50c2e29))
|
🎉 This PR is included in version 2.64.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |




Background
captureIntegrationSpecificIds.V2(with a dot), but the SDK constant was defined ascaptureIntegrationSpecificIdsV2(no dot)What Has Changed
Screenshot showing the

.sent down from the serverChecklist