Skip to content

publish: getsentry/sentry-javascript@10.77.1 #10030

Closed

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
  • npm[@sentry/types]
  • npm[@sentry/node-core]
  • npm[@sentry/tanstackstart]

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


📋 Changelog

Important Changes

  • fix(v10/deps)!: Limit @opentelemetry/api to <1.10.0 and the OpenTelemetry SDK to <3.0.0 (#25715)

    Breaking change

    If your app uses @opentelemetry/api 1.10.0 or OpenTelemetry SDK v3 together with v10 of the Sentry SDK, you must stay on @opentelemetry/api below 1.10.0 and OpenTelemetry SDK v2, or upgrade to v11.

    @opentelemetry/api 1.10.0 only works with OpenTelemetry SDK v3 (@opentelemetry/core 3.x, @opentelemetry/instrumentation 0.300.x). The SDK v2 packages that v10 uses only support @opentelemetry/api below 1.10.0, and SDK v3 needs Node.js 22.15.0 or newer, while v10 supports Node.js 18 and newer. For this reason, v10 now limits @opentelemetry/api to <1.10.0, and the @opentelemetry/instrumentation and @opentelemetry/exporter-trace-otlp-http peer dependencies of @sentry/node-core to <0.300.0.

    If your app depends on @opentelemetry/api directly, use a version below 1.10.0 (for example ~1.9.1). With 1.10.0, your app and the Sentry SDK use different copies of the API, and the OpenTelemetry calls of your app do not see the tracer provider of the Sentry SDK.

    To use @opentelemetry/api 1.10.0 and OpenTelemetry SDK v3, upgrade to v11 of the Sentry SDK. For the upgrade steps, see the migration guide.

Other Changes

  • fix(v10/aws-serverless): End the function.aws span when a callback-style handler calls back (#25693)
  • fix(v10/build): Make CJS re-exports visible to Node ESM imports (#25690)
  • fix(v10/bundler-plugins): Inject the release only into chunks that load at startup (#25695)
  • fix(v10/cloudflare): auto-instrument a re-exported default export (#25407)
  • fix(v10/cloudflare): Bind a default re-export with var in the Vite transform (#25733)
  • fix(v10/cloudflare): keep default exports intact when auto-instrumenting (#25732)
  • fix(v10/nitro): Use forward slashes for resolved plugin paths on Windows (#25692)
  • fix(v10/node): Only read JavaScript and TypeScript source files in ContextLines (#25699)
  • fix(v10/node): Read module versions from the isolated layouts of pnpm and Bun (#25698)
  • fix(v10/react): Don't crash ErrorBoundary when error.cause is not an Error (#25691)
  • fix(v10/react): Match React Router navigations against root routes only (#25694)
  • fix(v10/replay): Apply attribute masking to breadcrumb messages (#25697)
Internal Changes
  • ci(v10): Cache Playwright browsers on v10 (#25720)
  • test(v10/e2e): Pull Supabase images from GHCR (#25719)
  • test(v10/e2e): Use Node 22.23.4 in E2E test apps (#25687)

Activity

  1. github-actions commented on Oct 27, 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 27, 2026
  3. getsantry commented on Oct 27, 2026

    @getsantry

    CI checks failed for getsentry/sentry-javascript@10.77.1 (8058db31). Publishing is blocked.

    Failed checks: All required jobs passed or were skipped, E2E webpack-5 Test, E2E vue-tanstack-router Test, E2E sveltekit-2.5.0-twp Test, E2E tanstack-router (basepath) Test, E2E sveltekit-cloudflare-pages Test, E2E sveltekit-2-svelte-5 Test, E2E sveltekit-2-orchestrion Test, E2E react-router-7-framework-spa-node-20-18 Test, E2E solid Test, E2E react-router-7-framework (latest) Test, E2E react-router-7-framework-spa Test, E2E react-router-8-spa Test, E2E react-router-8-framework Test, E2E react-router-8-spa (TS 3.8) Test, E2E react-router-7-framework-custom Test, E2E react-create-browser-router Test, E2E node-express-incorrect-instrumentation Test, E2E react-router-5 Test, E2E node-profiling-esm Test, E2E nuxt-3-dynamic-import Test, E2E node-fastify-5 Test, E2E node-express-esm-without-loader Test, E2E node-core-express-otel-v2 Test, E2E nextjs-custom-otel (webpack) Test, E2E nextjs-16-tunnel (handler, webpack, edge) Test, E2E node-core-express-otel-v2-sdk-node Test, E2E nextjs-15-t3 Test, E2E node-express-cjs-preload Test, E2E nextjs-16-cacheComponents Test, E2E node-core-light-express Test, E2E nextjs-16-cf-workers Test, E2E nextjs-14 Test, E2E nextjs-13 Test, E2E nestjs-basic-with-graphql Test, E2E effect-4-node Test, E2E create-react-app Test, E2E nestjs-8 Test, E2E hono-4 Test, E2E create-remix-app-v2 (orchestrion) Test, E2E hono-4 (deno) Test, E2E hono-4 (node) Test, E2E astro-6 Test, E2E cloudflare-mcp Test, E2E angular-17 Test, E2E astro-7-orchestrion Test, E2E astro-7-sourcemaps (static output) Test, E2E angular-22 Test, E2E aws-serverless-layer (Node 18) Test, E2E astro-7-sourcemaps Test, PW loader_replay_buffer Tests, PW loader_tracing Tests, PW loader_eager Tests

    View check runs

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

  4. added
    acceptedAdd to approve the deploy
    and removed
    ci-failedCI checks failed on the release branch
    on Oct 27, 2026
  5. github-actions commented on Oct 27, 2026

    @github-actions

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

  6. added
    ci-readyCI passed, safe to publish without polling
    and removed
    ci-pendingCI signal expected but not yet received
    on Oct 27, 2026
  7. getsantry commented on Oct 27, 2026

    @getsantry

    CI checks passed for getsentry/sentry-javascript@10.77.1. Publishing is starting now.

  8. github-actions commented on Oct 27, 2026

    @github-actions

    Publishing: run#40492520506

  9. github-actions commented on Oct 27, 2026

    @github-actions

    Published successfully: run#40492520506

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-readyCI passed, safe to publish without polling

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions