JavaScript SDK Releases — June 2026 (detailed)#137
Open
stephanie-anderson wants to merge 3 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
stephanie-anderson
force-pushed
the
sdk-releases-june-2026/javascript-detailed
branch
from
440779a to
11106a5
Compare
…nd real dates Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-Authored-By: rahul <rahul.chhabria@sentry.io> Co-Authored-By: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
stephanie-anderson
force-pushed
the
sdk-releases-june-2026/javascript-detailed
branch
from
11106a5 to
19cf911
Compare
andreiborza
reviewed
Jul 9, 2026
andreiborza
left a comment
andreiborza
left a comment
Member
There was a problem hiding this comment.
Nice, looks good overall. Some suggestion to drop stuff that is not user-facing.
|
|
||
| - `streamGenAiSpans` is now enabled by default — `gen_ai` spans stream as v2 envelope items, preventing drops and disabling default message truncation; self-hosted users can opt out with `streamGenAiSpans: false`. | ||
| - Expanded Cloudflare instrumentation: R2 buckets, D1 batch/exec/withSession, SQLite Durable Objects SQL API, and sync KV are all now auto-instrumented. | ||
| - `vercelAiIntegration` adds Vercel AI SDK v7 support; AWS SDK clients ≥ 3.1046.0 are auto-instrumented; Bun and Deno get orchestrion runtime hooks. |
Member
There was a problem hiding this comment.
Suggested change
| - `vercelAiIntegration` adds Vercel AI SDK v7 support; AWS SDK clients ≥ 3.1046.0 are auto-instrumented; Bun and Deno get orchestrion runtime hooks. | |
| - `vercelAiIntegration` adds Vercel AI SDK v7 support |
We don't want to highlight these to users.
|
|
||
| ## TL;DR | ||
|
|
||
| - `streamGenAiSpans` is now enabled by default — `gen_ai` spans stream as v2 envelope items, preventing drops and disabling default message truncation; self-hosted users can opt out with `streamGenAiSpans: false`. |
Member
There was a problem hiding this comment.
Suggested change
| - `streamGenAiSpans` is now enabled by default — `gen_ai` spans stream as v2 envelope items, preventing drops and disabling default message truncation; self-hosted users can opt out with `streamGenAiSpans: false`. | |
| - `streamGenAiSpans` is now enabled by default — `gen_ai` spans are sent as v2 envelope items, preventing size limit drops and disabling default message truncation; self-hosted users can opt out with `streamGenAiSpans: false`. |
| - `streamGenAiSpans` is now enabled by default — `gen_ai` spans stream as v2 envelope items, preventing drops and disabling default message truncation; self-hosted users can opt out with `streamGenAiSpans: false`. | ||
| - Expanded Cloudflare instrumentation: R2 buckets, D1 batch/exec/withSession, SQLite Durable Objects SQL API, and sync KV are all now auto-instrumented. | ||
| - `vercelAiIntegration` adds Vercel AI SDK v7 support; AWS SDK clients ≥ 3.1046.0 are auto-instrumented; Bun and Deno get orchestrion runtime hooks. | ||
| - New top-level `Sentry.setAttribute(s)` APIs; Hono transactions named after matched route handlers; `bindScopeToEmitter` for event-emitter-scoped traces. |
Member
There was a problem hiding this comment.
Suggested change
| - New top-level `Sentry.setAttribute(s)` APIs; Hono transactions named after matched route handlers; `bindScopeToEmitter` for event-emitter-scoped traces. | |
| - New top-level `Sentry.setAttribute(s)` APIs; Hono transactions named after matched route handlers |
This is not user-facing.
|
|
||
| Cloudflare storage instrumentation expanded across four releases: 10.60.0 added R2 bucket auto-instrumentation, 10.61.0 added D1 batch operations, `exec()`, and `withSession()`, as well as SQL API instrumentation for SQLite Durable Objects. 10.59.0 added synchronous KV instrumentation. Together these give complete zero-config coverage for Cloudflare storage primitives. | ||
|
|
||
| 10.62.0 extends `vercelAiIntegration` to support v7 of the Vercel AI SDK (note: not yet available on Cloudflare Workers). In 10.59.0, AWS SDK clients at v3.1046.0 or later are automatically instrumented. Bun gained an orchestrion build plugin in 10.59.0 and Deno a runtime hook, enabling zero-config instrumentation for those runtimes. |
Member
There was a problem hiding this comment.
Suggested change
| 10.62.0 extends `vercelAiIntegration` to support v7 of the Vercel AI SDK (note: not yet available on Cloudflare Workers). In 10.59.0, AWS SDK clients at v3.1046.0 or later are automatically instrumented. Bun gained an orchestrion build plugin in 10.59.0 and Deno a runtime hook, enabling zero-config instrumentation for those runtimes. | |
| 10.62.0 extends `vercelAiIntegration` to support v7 of the Vercel AI SDK (note: not yet available on Cloudflare Workers). |
We don't want to highlight these to users.
|
|
||
| 10.62.0 extends `vercelAiIntegration` to support v7 of the Vercel AI SDK (note: not yet available on Cloudflare Workers). In 10.59.0, AWS SDK clients at v3.1046.0 or later are automatically instrumented. Bun gained an orchestrion build plugin in 10.59.0 and Deno a runtime hook, enabling zero-config instrumentation for those runtimes. | ||
|
|
||
| 10.61.0 adds two new top-level APIs — `Sentry.setAttribute(key, value)` and `Sentry.setAttributes(attributes)` — for setting custom attributes on the currently active span without a direct span reference. Hono transactions are now named after the matched route handler. 10.60.0 introduces `bindScopeToEmitter(emitter)`, which propagates the active Sentry scope to all listeners of a Node.js `EventEmitter`. |
Member
There was a problem hiding this comment.
Suggested change
| 10.61.0 adds two new top-level APIs — `Sentry.setAttribute(key, value)` and `Sentry.setAttributes(attributes)` — for setting custom attributes on the currently active span without a direct span reference. Hono transactions are now named after the matched route handler. 10.60.0 introduces `bindScopeToEmitter(emitter)`, which propagates the active Sentry scope to all listeners of a Node.js `EventEmitter`. | |
| 10.61.0 adds two new top-level APIs — `Sentry.setAttribute(key, value)` and `Sentry.setAttributes(attributes)` — for setting custom attributes on the currently active span without a direct span reference. Hono transactions are now named after the matched route handler. |
This is not user-facing.
Remove AWS/Bun/Deno and bindScopeToEmitter callouts, and tighten the streamGenAiSpans wording based on reviewer feedback. Co-Authored-By: rahul <rahul.chhabria@sentry.io>
rahulchhabria
left a comment
rahulchhabria
left a comment
Contributor
There was a problem hiding this comment.
Addressed @andreiborza's review:
- Dropped AWS/Bun/Deno and
bindScopeToEmittercallouts (not user-facing) - Tightened
streamGenAiSpanswording - Kept Vercel AI SDK v7 +
setAttribute(s)/ Hono as the user-facing highlights
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Seer correctly flagged "four releases" vs three listed versions (10.59.0, 10.60.0, 10.61.0). Co-Authored-By: rahul <rahul.chhabria@sentry.io>
rahulchhabria
left a comment
rahulchhabria
left a comment
Contributor
There was a problem hiding this comment.
Fixed Seer finding: Cloudflare instrumentation is across three releases (10.59.0, 10.60.0, 10.61.0), not four.
|
|
||
| 10.56.0 fixes `instrumentDurableObjectWithSentry` accidentally breaking Cloudflare Agents when applied to Durable Objects that use the Agents SDK. | ||
|
|
||
| 10.62.0 makes the SDK resilient to runtimes where `tracingChannel` is not available (Node < 22), instead of throwing at runtime. |
Contributor
There was a problem hiding this comment.
Bug: The changelog incorrectly states that tracingChannel is unavailable in "Node < 22". The API is actually available starting from Node.js v18.19.0.
Severity: LOW
Suggested Fix
Update the changelog to reflect the correct Node.js version boundary where tracingChannel is unavailable. The text should be corrected to state that the fix applies to Node.js versions older than v18.19.0, not "Node < 22".
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: content/changelog/2026-06-javascript-sdk-releases.md#L59
Potential issue: The changelog entry claims that SDK version 10.62.0 adds resilience for
runtimes where `tracingChannel` is unavailable, specifying this as "Node < 22". This is
factually incorrect. According to official Node.js documentation, the `tracingChannel`
API was introduced in Node.js v18.19.0 and v19.9.0. Therefore, it is available in
versions 18.19+, 19.9+, 20.x, and 21.x. Publishing this inaccurate version information
will mislead users about which Node.js versions benefit from this SDK fix.
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.
Builds on #124 with three improvements:
## What changed→## TL;DR--
View Junior Session in Sentry