You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. New traceLifecycle: 'stream' init option (server-side SDKs)
PR #19119 introduces a new top-level Sentry.init() option for server-side SDKs:
// Server-side SDKs (node, nextjs, nestjs)Sentry.init({traceLifecycle: 'stream',// NEW — opt into span streamingtracesSampleRate: 0.5,beforeSendSpan: Sentry.withStreamedSpan(span=>{span.name='...';returnspan;}),// beforeSendTransaction has no effect in streaming mode});
The skills for sentry-node-sdk, sentry-nextjs-sdk, and sentry-nestjs-sdk do not mention traceLifecycle in their configuration reference tables.
2. New spanStreamingIntegration() for browser
Browser SDKs gain a new opt-in integration:
// Browser SDKs (browser, react, svelte)Sentry.init({integrations: [Sentry.spanStreamingIntegration(),// NEW — opt into span streamingSentry.browserTracingIntegration(),],tracesSampleRate: 0.5,beforeSendSpan: Sentry.withStreamedSpan(span=>{span.name='...';returnspan;}),});
The skills for sentry-browser-sdk, sentry-react-sdk, and sentry-svelte-sdk do not mention spanStreamingIntegration in their integration tables or tracing references.
3. New withStreamedSpan() helper
When span streaming is enabled, beforeSendSpan callbacks must be wrapped with Sentry.withStreamedSpan() to indicate SDK compatibility. The existing skills document beforeSendSpan without mentioning this new requirement.
4. beforeSendTransaction behavior change
When traceLifecycle: 'stream' is active (server) or spanStreamingIntegration is added (browser), beforeSendTransactionhas no effect. Skills that document beforeSendTransaction should note this.
Why This Needs Manual Review
Span Streaming is a new opt-in feature — the existing examples remain valid for users who don't opt in, so we need to add new content rather than replace existing content
Multiple skill files need coordinated updates: SKILL.md (init options / integration table) and references/tracing.md (new section on span streaming)
The feature is complex enough to warrant a dedicated subsection explaining when and why to enable it
The behavior difference between server (traceLifecycle) and browser (spanStreamingIntegration) needs clear documentation
MEDIUM — new opt-in feature; existing tracing setup remains valid for users who don't opt in, but the new APIs are missing entirely from all skill files.
Note
🔒 Integrity filter blocked 9 items
The following items were blocked because they don't meet the GitHub integrity level.
#282list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#20205list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#20203list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#7768list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#5067list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#5966list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#5951list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#2182list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
#83list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
cc
@getsentry/team-javascript-sdksSDK Changes Detected
The following PR was merged to
getsentry/sentry-javascriptthat affects all JavaScript SDK skills:Potential Skill Gaps
1. New
traceLifecycle: 'stream'init option (server-side SDKs)PR
#19119introduces a new top-levelSentry.init()option for server-side SDKs:The skills for
sentry-node-sdk,sentry-nextjs-sdk, andsentry-nestjs-sdkdo not mentiontraceLifecyclein their configuration reference tables.2. New
spanStreamingIntegration()for browserBrowser SDKs gain a new opt-in integration:
The skills for
sentry-browser-sdk,sentry-react-sdk, andsentry-svelte-sdkdo not mentionspanStreamingIntegrationin their integration tables or tracing references.3. New
withStreamedSpan()helperWhen span streaming is enabled,
beforeSendSpancallbacks must be wrapped withSentry.withStreamedSpan()to indicate SDK compatibility. The existing skills documentbeforeSendSpanwithout mentioning this new requirement.4.
beforeSendTransactionbehavior changeWhen
traceLifecycle: 'stream'is active (server) orspanStreamingIntegrationis added (browser),beforeSendTransactionhas no effect. Skills that documentbeforeSendTransactionshould note this.Why This Needs Manual Review
SKILL.md(init options / integration table) andreferences/tracing.md(new section on span streaming)traceLifecycle) and browser (spanStreamingIntegration) needs clear documentationSkill Files to Review
skills/sentry-node-sdk/SKILL.md+references/tracing.mdskills/sentry-browser-sdk/SKILL.md+references/tracing.mdskills/sentry-nextjs-sdk/SKILL.md+references/tracing.mdskills/sentry-react-sdk/SKILL.md+references/tracing.mdskills/sentry-nestjs-sdk/SKILL.md+references/tracing.mdskills/sentry-svelte-sdk/SKILL.md+references/tracing.mdPriority
MEDIUM — new opt-in feature; existing tracing setup remains valid for users who don't opt in, but the new APIs are missing entirely from all skill files.
Note
🔒 Integrity filter blocked 9 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: