build: Bump Sentry JS SDK to 10.61.0 and enable span streaming#1120
Open
cleptric wants to merge 2 commits into
Open
build: Bump Sentry JS SDK to 10.61.0 and enable span streaming#1120cleptric wants to merge 2 commits into
cleptric wants to merge 2 commits into
Conversation
Upgrade @sentry/cloudflare, @sentry/core, @sentry/node, and @sentry/react from 10.54.0 to 10.59.0. Enable the span streaming trace lifecycle across all environments so spans are sent individually as they complete instead of being batched into transactions. Server-side (mcp-server, mcp-test-client, cloudflare worker): traceLifecycle: 'stream' Browser-side (cloudflare client): spanStreamingIntegration() Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Lms24
approved these changes
Jun 26, 2026
Bump from 10.59.0 to 10.61.0 for Sentry.setAttribute support. Mirror initialScope.tags to initialScope.attributes across all Sentry configs (cloudflare, stdio server, test client) for span attribute propagation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
cleptric
changed the title
Lms24
approved these changes
Jun 30, 2026
Lms24
left a comment
Lms24
left a comment
Member
There was a problem hiding this comment.
It seems like we call setTag a bunch of times. we likely want to convert these calls to attributes. The skill was already updated to make this migration but since our release to agent plugin marketplaces is broken, you might need to run the skill manually.
Besides the setAttribute calls, LGTM, so ✅ing.
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
2 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.
We're dropping a small number of transactions/spans due to size limits. Migrating to span streaming to improve this.
Upgrade
@sentry/cloudflare,@sentry/core,@sentry/node, and@sentry/reactfrom 10.54.0 to 10.61.0 and enable the span streaming trace lifecycle so spans
are sent in batches as they complete instead of being emitted when the transaction finishes.
Server-side configs (
mcp-server,mcp-test-client, cloudflare worker) gettraceLifecycle: 'stream'. The browser client (mcp-cloudflare) getsspanStreamingIntegration()added to the integrations array, which enablesstreaming automatically.