Skip to content

publish: getsentry/sentry-javascript@10.77.0 #9952

Open

Description

@sentry-release-bot

Requested by: @andreiborza

Merge target: v10

Quick links:

Assign the accepted label to this issue to approve the release.

Targets

  • npm[@sentry/core]
  • npm[@sentry/server-utils]
  • npm[@sentry/server-runtime-injection]
  • npm[@sentry/browser-utils]
  • npm[@sentry/replay]
  • npm[@sentry/opentelemetry]
  • npm[@sentry/feedback]
  • npm[@sentry/replay-canvas]
  • npm[@sentry/browser]
  • npm[@sentry/node]
  • npm[@sentry/profiling-node]
  • npm[@sentry/node-native]
  • npm[@sentry/angular]
  • npm[@sentry/ember]
  • npm[@sentry/react]
  • npm[@sentry/solid]
  • npm[@sentry/svelte]
  • npm[@sentry/vue]
  • npm[@sentry/wasm]
  • npm[@sentry/vercel-edge]
  • npm[@sentry/cloudflare]
  • npm[@sentry/deno]
  • npm[@sentry/aws-serverless]
  • npm[@sentry/google-cloud-serverless]
  • npm[@sentry/bun]
  • npm[@sentry/elysia]
  • npm[@sentry/hono]
  • npm[@sentry/nestjs]
  • npm[@sentry/effect]
  • npm[@sentry/nextjs]
  • npm[@sentry/nuxt]
  • npm[@sentry/remix]
  • npm[@sentry/solidstart]
  • npm[@sentry/sveltekit]
  • npm[@sentry/tanstackstart-react]
  • npm[@sentry/gatsby]
  • npm[@sentry/astro]
  • npm[@sentry/react-router]
  • npm[@sentry/nitro]
  • npm[@sentry/bundler-plugins]
  • npm[@sentry/esbuild-plugin]
  • npm[@sentry/rollup-plugin]
  • npm[@sentry/vite-plugin]
  • npm[@sentry/webpack-plugin]
  • npm[@sentry/typescript]
  • npm[@sentry/eslint-plugin-sdk]
  • npm[@sentry/eslint-config-sdk]
  • aws-lambda-layer
  • gcs[browser-cdn-bundles]
  • github
  • registry

Checked targets will be skipped (either already published or user-requested skip). Uncheck to retry a target.


📋 Changelog

Important Changes

  • feat(v10/nextjs): Add a tunnel route handler that sends only the event payload to Sentry (#25559)

    The tunnelRoute option can now send events through a route handler in your app. The handler forwards only the event payload to Sentry, and no request headers. To use it, add this file next to your tunnelRoute option:

    // app/sentry-tunnel/route.ts (or src/app/sentry-tunnel/route.ts)
    export { POST } from '@sentry/nextjs/tunnel';

    The handler accepts events for the DSN of your server SDK. To accept other DSNs, use createSentryTunnelRoute({ allowedDsns }) from the same import. Without the file, the tunnel route works as before.

    With the handler, tunnel requests go through your middleware. If your middleware blocks unauthenticated requests, exclude the tunnel route in its matcher.

    Also, the server no longer sends spans of tunnel requests when span streaming is on, because these spans only show the SDK's own traffic.

  • feat(v10/nextjs): Send tunnel route requests with credentials: 'omit' (#25561)

    With tunnelRoute and no tunnel route handler, @sentry/nextjs now sends events from the browser with credentials: 'omit', because the tunnel route does not need cookies.
    If a layer in front of your app checks cookies before it lets requests through (for example Vercel Deployment Protection), you can send them again in your browser Sentry.init call:

    // instrumentation-client.ts
    Sentry.init({
      transportOptions: { fetchOptions: { credentials: 'same-origin' } },
    });

Other Changes

  • feat(v10/core): Limit the body size of tunnel requests (#25560)
  • fix(v10/astro): Upload source maps of Astro 7's prerender build (#25426)
  • fix(v10/browser): Apply urlQueryParams to event URLs, static span names and LCP URLs (#25297)
  • fix(v10/browser): Apply urlQueryParams to the Referer header (#25425)
  • fix(v10/browser): Skip profiling for unsampled active root spans (#25502)
  • fix(v10/bundler-plugins): Check globalThis before global in the injected snippet (#25507)
  • fix(v10/bundler-plugins): Escape JSON in generated injection code (#25298)
  • fix(v10/cloudflare): auto-instrument when wrangler main is a package (#25430)
  • fix(v10/core): Don't mark http client spans as errors when the caller aborts (#25431)
  • fix(v10/core): Record span outcomes for spans dropped when building a transaction (#25294)
  • fix(v10/core): Stop treating previous_response_id as the OpenAI conversation id (#25432)
  • fix(v10/hono): Expose runtime-specific SDK options (#25299)
  • fix(v10/nextjs): Apply top-level bundleSizeOptimizations to webpack and Turbopack builds (#25261)
  • fix(v10/nextjs): Filter query parameters in request error context (#25433)
  • fix(v10/nextjs): Only inject applicationKey metadata into browser bundles (#25567)
  • fix(v10/node): Don't mark fetch spans as errors when the caller aborts (#25273)
  • fix(v10/nuxt): Delete public source maps before Nitro lists its public assets (#25284)
  • fix(v10/nuxt): Keep sourcesContent in Nuxt 5 server source maps (#25499)
  • fix(v10/nuxt): Skip 3xx/4xx Nuxt errors in the vue:error hook (#25427)
  • fix(v10/react-router): Respect custom default integrations (#25434)
  • fix(v10/remix): Respect custom default integrations (#25435)
  • fix(v10/server-utils): End Express layer spans when the client aborts (#25256)
  • fix(v10/server-utils): avoid quadratic SQL summary regex backtracking (#25257)
  • fix(v10/sveltekit): add op and origin to Kit's sveltekit.endpoint span (#25429)
  • fix(v10/tanstackstart-react): Keep parametrized route names in Nitro 3 builds (#25316)
  • fix(v10/tanstackstart-react): Rewrite source paths of split route modules (#25428)
Internal Changes
  • ci(v10): Assign Junior backport PRs to the original author (#25529)
  • test(v10): Skip Vercel AI OTel multi-step test on Node 26.12+ (#25443)
  • test(v10/cloudflare): Deflake flush-timeout Workflow test (#25182)
  • test(v10/e2e): Update TanStack Start build tooling (#25436)
  • test(v10/sveltekit): Pin rollup to 4.64.5 (#25440)

Activity

  1. github-actions commented on Oct 21, 2026

    @github-actions

    Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.

  2. added
    ci-failedCI checks failed on the release branch
    and removed
    acceptedAdd to approve the deploy
    ci-pendingCI signal expected but not yet received
    on Oct 21, 2026
  3. getsantry commented on Oct 21, 2026

    @getsantry

    CI checks failed for getsentry/sentry-javascript@10.77.0 (4224a821). Publishing is blocked.

    Failed checks: All required jobs passed or were skipped, E2E node-otel-without-tracing Test, E2E node-otel-custom-sampler Test, E2E node-core-express-otel-v2-custom-sampler Test, E2E node-core-express-otel-v1-custom-sampler Test, E2E astro-7-orchestrion Test, E2E astro-7-sourcemaps (static output) Test, E2E astro-7-sourcemaps Test, Node (18) Integration Tests, Node (26) Integration Tests, Node (24) Integration Tests, Node (24) (TS 3.8) Integration Tests, Node (22) Integration Tests, Node (20) Integration Tests

    View check runs

    Re-add the accepted label once CI is fixed to retry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ci-failedCI checks failed on the release branch

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions