Skip to content

JavaScript SDK Releases — June 2026 (detailed) #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rahulchhabria merged 4 commits into from
Jul 15, 2026
Merged

JavaScript SDK Releases — June 2026 (detailed) #137

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
19cf911
feat(sdk): expand June 2026 release notes for javascript with prose a…
stephanie-anderson Jul 9, 2026
32e12b6
docs(javascript): drop non-user-facing notes per review
sentry-junior[bot] Jul 11, 2026
93cd33e
docs(javascript): fix Cloudflare release count in release notes
sentry-junior[bot] Jul 11, 2026
2381685
docs(javascript): correct tracingChannel Node version in release notes
rahulchhabria Jul 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 40 additions & 16 deletions content/changelog/2026-06-javascript-sdk-releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,22 +14,46 @@ date: 2026-06-30
author: rahulchhabria@sentry.io
---

Releases covered: **10.56.0 · 10.57.0 · 10.58.0 · 10.59.0 · 10.60.0 · 10.61.0 · 10.62.0**
Releases covered:

| Version | Date | Link |
|---------|------|------|
| 10.62.0 | Jun 2026 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.62.0) |
| 10.61.0 | Jun 2026 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.61.0) |
| 10.60.0 | Jun 2026 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.60.0) |
| 10.59.0 | Jun 2026 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.59.0) |
| 10.58.0 | Jun 2026 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.58.0) |
| 10.57.0 | Jun 2026 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.57.0) |
| 10.56.0 | Jun 2026 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.56.0) |

## What changed

- **gen_ai span streaming on by default (10.61.0):** `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 (10.60.0 · 10.61.0):** R2 buckets, D1 batch/exec/withSession, SQLite Durable Objects SQL API, and sync KV are all now auto-instrumented.
- **New integrations & runtime support (10.59.0 · 10.62.0):** `vercelAiIntegration` adds Vercel AI SDK v7 support; AWS SDK clients ≥ 3.1046.0 are auto-instrumented; Bun and Deno get orchestrion runtime hooks.
- **New APIs (10.61.0):** Top-level `Sentry.setAttribute(s)` APIs added; Hono transactions now named after matched route handlers; `bindScopeToEmitter` added for event-emitter-scoped traces.
- **Bug fixes (10.57.0 · 10.58.0):** React Router v6/v7 navigation detection moved to layout effect for correct trace propagation; PostgresJS no longer emits duplicate spans per query; Next.js redirects no longer reported as `internal_error`.
| 10.62.0 | 2026-06-26 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.62.0) |
| 10.61.0 | 2026-06-25 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.61.0) |
| 10.60.0 | 2026-06-23 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.60.0) |
| 10.59.0 | 2026-06-19 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.59.0) |
| 10.58.0 | 2026-06-15 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.58.0) |
| 10.57.0 | 2026-06-09 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.57.0) |
| 10.56.0 | 2026-06-02 | [Release notes](https://github.com/getsentry/sentry-javascript/releases/tag/10.56.0) |

## TL;DR

- `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`.
- 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
- New top-level `Sentry.setAttribute(s)` APIs; Hono transactions named after matched route handlers
- React Router v6/v7 navigation tracing fix; PostgresJS duplicate span fix; Next.js redirect classification fix.

## Release notes

### New Features

10.61.0 enables `streamGenAiSpans` by default. `gen_ai` spans are extracted from transactions and sent as v2 envelope items, which means they can no longer be dropped when the transaction payload exceeds size limits, and AI message data is no longer truncated by default. Pass `enableTruncation: true` on the respective AI integration to re-enable truncation. Self-hosted Sentry users should set `streamGenAiSpans: false` until their instance supports streamed spans.

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.
Comment thread
sentry[bot] marked this conversation as resolved.
Outdated

10.62.0 extends `vercelAiIntegration` to support v7 of the Vercel AI SDK (note: not yet available on Cloudflare Workers).

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.

### Bug Fixes

10.57.0 moves React Router v6/v7 navigation detection from a regular effect to a layout effect. This ensures the correct parent trace is present when the navigation span is created, closing trace propagation gaps visible in distributed traces.

Also in 10.57.0, the PostgresJS integration was emitting a duplicate span for every query due to a listener registration bug. Only one span is now created per query.

In 10.58.0, Next.js server actions that perform redirects were incorrectly classified as `internal_error`. They are now reported as `ok`.

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.

@sentry sentry Bot Jul 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.