ci(e2e): Run E2E tests with pnpm 12 by s1gr1d · Pull Request #25334 · getsentry/sentry-javascript

s1gr1d · 2026-10-13T15:28:20Z

Moves the E2E tests from pnpm 9 to pnpm 12. Volta still manages node.

Every app has a pnpm-workspace.yaml. pnpm 11+ reads its settings only from this file.
- allowBuilds: pnpm 11+ fails the install on build scripts that are not listed. false is only for scripts that just print a message.
- minimumReleaseAge: 0: by default, pnpm 11+ installs only releases that are at least 24 hours old, and falls back to older versions. The apps test against the newest releases, so the E2E runner fails if an app does not set it.
Updated to @electron/rebuild ^4.2.1. Older versions depend on @electron/node-gyp from git, and pnpm 11+ blocks git dependencies of dependencies.
Ignored overrides fixed. The bundler-plugin fixtures had overrides in package.json#pnpm, and some apps used package.json#resolutions. pnpm 11+ ignores both without an error. The E2E runner now fails if an app still uses them.
Test app fixes for pnpm 12.
- The Next.js tests and build assertions read the installed version from next/package.json. pnpm add next@15 now saves ^15.x.y, and the old version checks did not work with the ^.
- The tanstackstart apps use "nitro": "^3.0.0", because pnpm 12 resolved latest || * to the placeholder nitro@0.0.0. This installs the same nitro@3.0.0 as pnpm 9. A follow-up moves them to the nitro beta, which needs Vite 8.
- 7 apps no longer run npx playwright install in test:build. CI already installs the app's Playwright version, and the second install ran at the same time and failed.

Why pnpm is a root dev dependency

pnpm switches to the version in a packageManager field, but a pnpm must already be installed to do that. Yarn installs that first pnpm as a dev dependency, because Volta can't run pnpm 12 and is unmaintained. The pnpm package is a native binary, so it does not depend on the node version that an app pins. yarn.lock pins the version, so local runs and CI use the same pnpm. Contributors need no extra setup, and CI caches pnpm with node_modules.

Rejected alternatives:

pnpm/action-setup alone: it only installs pnpm in CI. Contributors would have to install pnpm themselves, and their version could differ from CI.
Corepack: it is deprecated, and Node 25 no longer includes it.
mise: no getsentry JS repo uses it, and contributors would need one more tool (alongside Volta).

⚠️ @JPeer264 When the repo moves from Yarn to pnpm, remove the dev dependency and set packageManager in the root package.json. A test app can still pin another pnpm version (10.30 or newer, which reads allowBuilds) with its own packageManager field.

chore: Move the monorepo from Yarn 1 to pnpm 12 #25354

Volta cannot run pnpm 12, so pnpm is now a root devDependency. Volta only pins node per app. pnpm 11+ reads settings only from pnpm-workspace.yaml and blocks unlisted build scripts, so each app now has a pnpm-workspace.yaml with allowBuilds and minimumReleaseAge: 0.

mydea · 2026-10-14T14:11:15Z

    "typescript": "~5.8.3",
    "vite": "^7.3.2"
  },
  "volta": {


not directly related to this test, but we should actually replace these with a reference to the workspace volta config.

(I may open a PR to update this everywhere)

mydea · 2026-10-14T14:20:44Z

Semi related, opened #25369 to actually update volta config in e2e test apps to better align with the fact we are using node 24 anyhow now by default!

# Conflicts: # dev-packages/e2e-tests/test-applications/browser-bfcache/package.json # dev-packages/e2e-tests/test-applications/browser-mfe-vite/package.json # dev-packages/e2e-tests/test-applications/browser-webworker-vite/package.json # dev-packages/e2e-tests/test-applications/remix-v3/package.json

# Conflicts: # dev-packages/bundler-plugin-integration-tests/fixtures/esbuild/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/rolldown/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/rollup3/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/rollup4/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/vite4/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/vite6/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/vite7/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/vite8/package.json # dev-packages/bundler-plugin-integration-tests/fixtures/webpack5/package.json

JPeer264

LGTM. Just added nits mostly

JPeer264 · 2026-10-15T11:03:36Z

 - **Packed tarballs missing**: Run `yarn build:tarball` at the repo root, then `yarn test:prepare` in `dev-packages/e2e-tests`
 - **Build failures**: Fix build errors before running tests
- **pnpm errors such as `packages field missing or empty`**: The app needs the pnpm version in its `volta.pnpm`. Run with Volta, which installs that version
+- **`ERR_PNPM_IGNORED_BUILDS`**: A dependency has a build script that the app's `allowBuilds` does not list. Add it to the app's `pnpm-workspace.yaml`: `true` if the app needs the script, `false` if the script only prints a message


l: Theoretically pnpm approve-builds is adding it - maybe worth to add this here

JPeer264 · 2026-10-15T11:05:28Z

  steps:
-    - name: Resolve pnpm version
-      id: pnpm-version
+    # The devDependency is the one pnpm version for CI and local runs. An app that needs another version sets


super-l: It is weird that it is written devDependency and not "dev dependency" - maybe we can rename it to the latter. First I read it any thought that something is off 😅

Suggested change

# The devDependency is the one pnpm version for CI and local runs. An app that needs another version sets

# The dev dependency is the one pnpm version for CI and local runs. An app that needs another version sets

JPeer264 · 2026-10-15T11:12:16Z

@@ -0,0 +1 @@
+minimumReleaseAge: 0


q/l: Couldn't we make one more global pnpm-workspace.yaml in the e2e test root and copy it over into each directory? Theoretically we don't treat each folder as own workspace, but we potentially forget to set minimumRelaseAge: 0 on new tests.

If we keep it though, we should add a bugbot rule that this is set as a minimum on new e2e tests or make sure in our runners that this is set. wdyt?

I'll add a rule for that 👍

JPeer264 · 2026-10-15T11:16:25Z

    "react": "^19.2.0",
    "react-dom": "^19.2.0",
-    "nitro": "latest || *",
+    "nitro": "^3.0.0",


q: Is that change necessary in this PR? Or was it required to be changed

yes, listed in the PR description:

The tanstackstart apps use "nitro": "^3.0.0", because pnpm 12 resolved latest || * to the placeholder nitro@0.0.0. This installs the same nitro@3.0.0 as pnpm 9. A follow-up moves them to the nitro beta, which needs Vite 8.

Thanks for confirming. Sorry I forgot the PR description after scrolling through all the changes 😅

PR ref: #25451

JPeer264 · 2026-10-15T11:16:36Z

    "react": "^19.2.0",
    "react-dom": "^19.2.0",
-    "nitro": "latest || *",
+    "nitro": "^3.0.0",


same as https://github.com/getsentry/sentry-javascript/pull/25334/changes#r4282274277

Follow-up to #25334. The tanstackstart-react apps now use the nitro beta instead of the deprecated `nitro@3.0.0`. The beta needs Vite 8, so the apps also use Vite 8 and `@vitejs/plugin-react-swc` 4, which is the first version that supports Vite 8. The SDK still supports Vite 7. Only the test apps changed.

This moves the monorepo from Yarn 1 to pnpm 12.11.2 (`packageManager`): scripts, CI workflows, the release script and the contributor docs. Review it commit by commit: 1. A plain `pnpm import` of `yarn.lock`. Most of the added lines of the PR are here. 2. The dependency changes against that import: the root `workspace:*` entries, `h3` and `unstorage` for `@sentry/nitro` and `@sentry/nuxt`, the `yarn.lock` versions of the npm aliases (`pnpm import` resolves them again), and `pnpm dedupe`. 3. The move from Yarn to pnpm. This commit does not change the lockfile. 4. The bump to pnpm 12: the settings move to `pnpm-workspace.yaml`, the pnpm dev dependency of #25334 is removed, and `pnpm dedupe` with pnpm 12 merges 10 versions (no new versions). Other changes beyond the rename: - Scripts are called with `pnpm run <script>` and package binaries with `pnpm exec <bin>`. Volta's pnpm 9 rejects the options of `pnpm test` (for example `--watch`) before it switches to pnpm 12. - `@sentry/server-runtime-injection` vendors the same files as with Yarn. It declares `supports-color` 7.2.0, because pnpm installs another version next to `debug`, and it names vendored files by their path after the last `node_modules/`. - The Lambda layer build writes its overrides to a `pnpm-workspace.yaml` (pnpm 12 does not read `resolutions`), and it no longer writes through pnpm's hard links into `packages/core/build`. - The rollup bundler fixtures declare `@babel/preset-react`, like the webpack fixture. Their configs use it, and with Yarn they found it in the root `node_modules`. pnpm 12 installs it only in `packages/bundler-plugins/node_modules`. ## Install layout decisions `nodeLinker: hoisted` and `autoInstallPeers: false` give the same flat `node_modules` as Yarn 1. This is only for now, to make the switch from Yarn easier. The next PR moves to the isolated pnpm default, where every package must declare all its imports. ## Workspace decisions All workspace packages are root `devDependencies` (`workspace:*`), because some configs import workspace packages without declaring them. The next PR removes them. The `workspaces` list stays in `package.json` for Deno. `verify-packages-versions.js` checks that it matches the `packages` list of `pnpm-workspace.yaml`, and that every workspace package is in the root `devDependencies`. New packages must go into all three. ## pnpm version decisions This goes directly to pnpm 12, because a pnpm 9 root does not work with the pnpm 12 dev dependency of #25334: nested `pnpm` calls in scripts get pnpm 12, which refuses the pnpm 9 install. Volta cannot run pnpm 12.4 or newer ([volta-cli/volta#2114](volta-cli/volta#2114)), so it keeps pnpm 9.15.9, and `manage-package-manager-versions` in `.npmrc` switches it to the `packageManager` version. ## Known issues - The release and canary workflows did not run on this branch. A local simulation of 11.8.0 ran the pre-release script, the CI build, the tarballs and `npm publish --dry-run`. The tarballs have the same files as the published 11.7.0. - npm commands in the repo warn about `manage-package-manager-versions` in `.npmrc`. npm does not use this setting, but Volta's pnpm 9 needs it to switch to pnpm 12. - The Cursor cloud setup sets `VOLTA_FEATURE_PNPM=1` only in its own commands. A new shell that reads only `~/.bashrc` does not find pnpm. - Dependency Review (not a required check) fails, because it treats every package of the new lockfile as added. It reports advisories for `yarn.lock` versions that are dismissed in Dependabot. After the merge, it checks only lockfile changes again. --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

…25403) Each E2E job restored the full ~860 MB root dependency cache and the build output (about 33s per job, ~2.5 runner-hours per CI run) only to run a few `tsx` scripts and to resolve `@sentry-internal/test-utils`. Since #25402 installs test-utils from a tarball, E2E jobs now only download tarballs. The E2E scripts are now plain `.mjs` files without dependencies. They run under each app's pinned Node (down to 20.19), which rules out Node's type stripping. With `run.ts` converted too, the package no longer needs `tsx`, `dotenv`, `glob`, `esbuild` or a tsconfig (`lint:ts` never ran in CI). Since #25380 the Playwright install reads its version from the app's `package.json`, so it doesn't need the root `node_modules` either. Since #25334, `install-pnpm` takes pnpm from the root `node_modules` too, so the E2E jobs install the root `devDependencies` version with `pnpm/action-setup` instead. Other workflows and local runs keep getting pnpm through `yarn.lock`. `aws-serverless` still downloads the build output, since its Lambda stack installs the built package directories. Stacked on #25402. Replaces #25371, which GitHub closed as merged by accident during a restack. Its review history is still there. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

@4ktLuffy

| datasource | package | from | to | | ---------- | ------------------- | ------ | ------ | | npm | @sentry/vite-plugin | 11.8.0 | 11.9.0 | ## [v11.9.0](https://github.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#1190) ##### Important Changes - **feat: Rename `diagnostic_channel`, fetch and gRPC span origins ([#25601](getsentry/sentry-javascript#25601 Some span origins changed their names to match the other v11 origins: - `auto.graphql.diagnostic_channel` is now `auto.graphql.graphql`. - `auto.db.redis.diagnostic_channel`, `auto.db.mysql2.diagnostic_channel` and `auto.db.mongoose.diagnostic_channel` now end in `.native_channel`. - `auto.http.wintercg_fetch` is now `auto.http.fetch`, as on Bun, Deno and Cloudflare. - `auto.grpc.serverless` is now `auto.grpc.google_cloud`. If you have `ignoreSpans` rules, queries or alerts on the old origins, change them to use the new origins. - **feat(deno): Add incoming request options to `denoServeIntegration` ([#25493](getsentry/sentry-javascript#25493 `denoServeIntegration` now accepts `ignoreRequestBody`, `ignoreIncomingRequests`, `ignoreStaticAssets`, `spans`, `onSpanCreated` and `onSpanEnd`, with the same meaning as in `denoHttpIntegration`. The callbacks receive the web `Request`. `ignoreStaticAssets` defaults to `true`, so `Deno.serve` no longer creates spans for `GET` requests to common static assets such as `favicon.ico`, `robots.txt` or `*.js` files. To keep these spans, set `denoServeIntegration({ ignoreStaticAssets: false })`. `Deno.serve` spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. - **feat(deno): Record request sessions for `Deno.serve` ([#25496](getsentry/sentry-javascript#25496 `denoServeIntegration` now records a request session for each incoming request, as `denoHttpIntegration` does for `node:http`. This gives release health and crash-free rates for `Deno.serve` apps. Sessions are sent only when a `release` is set. To turn them off, set `denoServeIntegration({ sessions: false })`. `sessionFlushingDelayMS` sets how long the SDK waits before it sends the session aggregate. - **feat(deno): Register channel injection hooks from `init()` ([#25546](getsentry/sentry-javascript#25546 `Sentry.init()` in `@sentry/deno` now registers the diagnostics-channel injection hooks, as `@sentry/node` does. The channel integrations now record spans without `--preload=npm:@sentry/deno/import`, for modules that you import after `init()`. To also instrument modules that load before `init()`, such as static imports in your entry module, keep the preload. With `debug: true`, the SDK logs a warning when no injection is active. On Node.js, tracing-hooks messages now show with `debug: true` instead of with `DEBUG=@apm-js-collab/*`. - **feat(nextjs): Add a tunnel route handler that sends only the event payload to Sentry ([#25456](getsentry/sentry-javascript#25456 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: ```ts // 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. 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(nextjs): Never emit trace meta tags from a prerender ([#25141](getsentry/sentry-javascript#25141 Pageloads of apps with `cacheComponents` enabled are connected to their server request again. Pages that Next.js prerenders no longer carry trace information, so a cached page can no longer connect visitors to a request that was not theirs. This also applies to ISR pages. The pageload waits for the trace information when it arrives with the part of the page that streams in after a cached shell. If you set up OpenTelemetry yourself and register `SentryPropagator`, register `NextSentryPropagator` instead and pass your tracer provider to `markPrerendersOnTracerProvider`, so that your prerendered pages carry no trace information either. - **feat(nextjs): Send tunnel route requests with `credentials: 'omit'` ([#25509](getsentry/sentry-javascript#25509 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: ```js // instrumentation-client.ts Sentry.init({ transportOptions: { fetchOptions: { credentials: 'same-origin' } }, }); ``` - **feat(nitro): Report a single `http.server` span per request ([#25295](getsentry/sentry-javascript#25295 A Nitro request now creates only one `http.server` span. The nested `http.server` spans with the origins `auto.http.nitro.srvx` and `auto.http.nitro.h3` are removed. h3 route handlers now get a `handler` span, and middleware spans are direct children of the `http.server` span. If you have queries or alerts on the removed spans, change them to use the `http.server` span or the `handler` span. - **fix: Use `auto.http.http_server` origin for all `node:http` server spans ([#25604](getsentry/sentry-javascript#25604 On Bun and Deno, `node:http` server spans now have the origin `auto.http.http_server` instead of `auto.http.server`, as on Node.js. On Node.js, nothing changes. `Bun.serve` spans keep `auto.http.bun.serve` and `Deno.serve` spans keep `auto.http.deno`. If you have `ignoreSpans` or `beforeSendSpan` rules, queries or alerts on `auto.http.server`, change them to use `auto.http.http_server`. ##### Other Changes - feat(browser): Add `LoaderSentry` type export ([#25357](getsentry/sentry-javascript#25357)) - feat(cloudflare): Add `isStreamingResponse` option and detect streamed RSC responses ([#24932](getsentry/sentry-javascript#24932)) - feat(core): Add `dataCollection.mcp` option ([#25553](getsentry/sentry-javascript#25553)) - feat(core): Limit the body size of tunnel requests ([#25515](getsentry/sentry-javascript#25515)) - feat(nextjs): Link `use cache` hits to their fill across instances ([#25448](getsentry/sentry-javascript#25448)) - feat(nextjs): Wait for the resumed part of a document before starting the pageload ([#25142](getsentry/sentry-javascript#25142)) - feat(nitro): Merge the nitro integrations into a single `nitroIntegration` ([#25349](getsentry/sentry-javascript#25349)) - feat(server-utils): Emit `execute_tool` spans for Anthropic's `beta.messages.toolRunner()` ([#25320](getsentry/sentry-javascript#25320)) - fix(astro): defer to `@sentry/cloudflare/vite` on Cloudflare Workers ([#25347](getsentry/sentry-javascript#25347)) - fix(aws-serverless): End the `function.aws` span when a callback-style handler calls back ([#25543](getsentry/sentry-javascript#25543)) - fix(browser): Skip profiling for unsampled active root spans ([#25498](getsentry/sentry-javascript#25498)) - fix(bundler-plugins): Check `globalThis` before `global` in the injected snippet ([#25365](getsentry/sentry-javascript#25365)) - fix(bundler-plugins): Inject the release only into chunks that load at startup ([#25541](getsentry/sentry-javascript#25541)) - fix(cloudflare): auto-instrument a re-exported default export ([#25345](getsentry/sentry-javascript#25345)) - fix(cloudflare): Deliver check-ins and events from forked isolation scopes ([#25374](getsentry/sentry-javascript#25374)) - fix(cloudflare): Don't hold Durable Object invocations open with the segment-end flush timer ([#25490](getsentry/sentry-javascript#25490)) - fix(cloudflare): keep default exports intact when auto-instrumenting ([#25372](getsentry/sentry-javascript#25372)) - fix(core): Use `trace_metric` data category for metrics rate limits and client reports ([#25606](getsentry/sentry-javascript#25606)) - fix(deps): Allow `@opentelemetry/api` 1.9 again ([#25684](getsentry/sentry-javascript#25684)) - fix(deno): Re-export portable helpers that Cloudflare exposes ([#25491](getsentry/sentry-javascript#25491)) - fix(elysia): Set SDK metadata on the options passed to init ([#24521](getsentry/sentry-javascript#24521)) - fix(elysia): use Node transport on Node runtimes ([#25015](getsentry/sentry-javascript#25015)) - fix(hono): Read connection info from the runtime instead of Hono helpers ([#25552](getsentry/sentry-javascript#25552)) - fix(nextjs): Only inject applicationKey metadata into browser bundles ([#25565](getsentry/sentry-javascript#25565)) - fix(nitro): Use forward slashes for resolved plugin paths on Windows ([#25023](getsentry/sentry-javascript#25023)) - fix(node,vercel-edge,bundler-plugins): Ignore commit env vars set to their own name ([#25244](getsentry/sentry-javascript#25244)) - fix(node): Guard user callbacks in the `node:http` server instrumentation ([#25592](getsentry/sentry-javascript#25592)) - fix(node): Only read JavaScript and TypeScript source files in ContextLines ([#25535](getsentry/sentry-javascript#25535)) - fix(node): restore tsx runtime instrumentation ([#25351](getsentry/sentry-javascript#25351)) - fix(nuxt): Delete Sentry-enabled source maps from Nitro output directories ([#25450](getsentry/sentry-javascript#25450)) - fix(nuxt): Keep sourcesContent in Nuxt 5 server source maps ([#25325](getsentry/sentry-javascript#25325)) - fix(react): Don't crash ErrorBoundary when `error.cause` is not an Error ([#25542](getsentry/sentry-javascript#25542)) - fix(react): Match React Router navigations against root routes only ([#25336](getsentry/sentry-javascript#25336)) - fix(server-runtime-injection): Load ESM hook without the build/esm package.json marker ([#25562](getsentry/sentry-javascript#25562)) - fix(server-utils): Bundle the CommonJS dependencies of instrumented packages on Vite 8 ([#25523](getsentry/sentry-javascript#25523)) - fix(server-utils): Keep OpenAI decision confidence on Vercel AI decide spans ([#25457](getsentry/sentry-javascript#25457)) - fix(server-utils): Nest LangChain run spans under their parent run ([#25364](getsentry/sentry-javascript#25364)) - fix(server-utils): Stop the orchestrion Vite plugin from bundling the CJS build of [@sentry/server-utils](https://github.com/sentry/server-utils) ([#25359](getsentry/sentry-javascript#25359)) - fix(solidstart): Read server action route from the request's root span ([#25513](getsentry/sentry-javascript#25513)) - fix(tanstackstart-react): Delete only the source maps that Sentry enabled ([#25362](getsentry/sentry-javascript#25362)) - fix(vercel-edge): expose portable tracing and feature flag helpers ([#25377](getsentry/sentry-javascript#25377)) - ref(bundler-plugins): Drop [@babel/core](https://github.com/babel/core) peer dependency ([#25406](getsentry/sentry-javascript#25406)) - ref(nitro): Move channel-based instrumentation into [@sentry/server-utils](https://github.com/sentry/server-utils) ([#24861](getsentry/sentry-javascript#24861)) <details> <summary> <strong>Internal Changes</strong> </summary> - build(node): Bump Node to 24.22.1 ([#25634](getsentry/sentry-javascript#25634)) - chore: Add external contributor to CHANGELOG.md ([#25367](getsentry/sentry-javascript#25367)) - chore: Add external contributor to CHANGELOG.md ([#25468](getsentry/sentry-javascript#25468)) - chore: Add external contributor to CHANGELOG.md ([#25483](getsentry/sentry-javascript#25483)) - chore: Add external contributor to CHANGELOG.md ([#25485](getsentry/sentry-javascript#25485)) - chore: Add external contributor to CHANGELOG.md ([#25487](getsentry/sentry-javascript#25487)) - chore: Add external contributor to CHANGELOG.md ([#25500](getsentry/sentry-javascript#25500)) - chore: Add external contributor to CHANGELOG.md ([#25505](getsentry/sentry-javascript#25505)) - chore: Add external contributor to CHANGELOG.md ([#25596](getsentry/sentry-javascript#25596)) - chore: Add external contributor to CHANGELOG.md ([#25597](getsentry/sentry-javascript#25597)) - chore: Add external contributor to CHANGELOG.md ([#25611](getsentry/sentry-javascript#25611)) - chore: Move the monorepo from Yarn 1 to pnpm 12 ([#25354](getsentry/sentry-javascript#25354)) - chore: Update comments related to span links with latest info ([#25135](getsentry/sentry-javascript#25135)) - chore(bugbot): Flag new Cloudflare tests that wrap the worker by hand ([#25619](getsentry/sentry-javascript#25619)) - chore(deps-dev): Bump oxlint and oxfmt ([#25578](getsentry/sentry-javascript#25578)) - chore(deps-dev): Bump vue from 3.2.45 to 3.5.43 ([#25413](getsentry/sentry-javascript#25413)) - chore(deps): Bump `@types/node` to 20 ([#25501](getsentry/sentry-javascript#25501)) - chore(deps): Bump Playwright to 1.64.1 and pin it exactly ([#25382](getsentry/sentry-javascript#25382)) - chore(hono): Remove "ALPHA" from package.json description ([#25521](getsentry/sentry-javascript#25521)) - chore(size-limit): weekly auto-bump ([#25442](getsentry/sentry-javascript#25442)) - ci: Check bundle size increases per PR ([#24737](getsentry/sentry-javascript#24737)) - ci: Empty cached node_modules that have broken `.bin` scripts ([#25635](getsentry/sentry-javascript#25635)) - ci: Fail when a Playwright version drifts from the pinned one ([#25383](getsentry/sentry-javascript#25383)) - ci: Keep Namespace cache volumes complete and cache the pnpm binary ([#25569](getsentry/sentry-javascript#25569)) - ci: Move size check reruns into a local action ([#25600](getsentry/sentry-javascript#25600)) - ci: Read the Playwright version from package.json in install-playwright ([#25380](getsentry/sentry-javascript#25380)) - ci: Run GitHub Actions jobs on Namespace runners ([#25547](getsentry/sentry-javascript#25547)) - ci: Run optional E2E tests in a separate workflow ([#25548](getsentry/sentry-javascript#25548)) - ci: Run the Playwright install's npx outside the repo ([#25384](getsentry/sentry-javascript#25384)) - ci: Share the E2E test setup between build.yml and optional-e2e.yml ([#25616](getsentry/sentry-javascript#25616)) - ci: Stop uploading duplicate tarballs to the release artifact ([#25688](getsentry/sentry-javascript#25688)) - ci(cloudflare): Run the integration tests on the latest wrangler too ([#25508](getsentry/sentry-javascript#25508)) - ci(e2e): Run all E2E tests when CI config changes ([#25391](getsentry/sentry-javascript#25391)) - ci(e2e): Run E2E tests with pnpm 12 ([#25334](getsentry/sentry-javascript#25334)) - ci(e2e): Run E2E tests without restoring the monorepo's node_modules ([#25403](getsentry/sentry-javascript#25403)) - ci(e2e): Stop pnpm run from installing the workspace in E2E jobs ([#25514](getsentry/sentry-javascript#25514)) - ci(size-limit): Don't enforce size limits on release PRs ([#25631](getsentry/sentry-javascript#25631)) - docs: Add guide for testing SDK packages with pnpm link ([#25512](getsentry/sentry-javascript#25512)) - feat(deps): Bump [@actions/glob](https://github.com/actions/glob) from 0.6.1 to 0.7.0 ([#25411](getsentry/sentry-javascript#25411)) - feat(deps): Bump [@anthropic-ai/sdk](https://github.com/anthropic-ai/sdk) from 0.63.0 to 0.133.0 ([#25417](getsentry/sentry-javascript#25417)) - feat(deps): Bump recast from 0.20.5 to 0.24.0 ([#25416](getsentry/sentry-javascript#25416)) - ref(core): Share the commit env var list used for release detection ([#25478](getsentry/sentry-javascript#25478)) - test(browser): Use blocking scripts in loader integration tests ([#25395](getsentry/sentry-javascript#25395)) - test(deps): Upgrade TanStack Start, Router, and Nitro ([#25445](getsentry/sentry-javascript#25445)) - test(e2e): Add node-otel-sdk-node-v3 e2e app for OpenTelemetry JS v3 ([#25630](getsentry/sentry-javascript#25630)) - test(e2e): Align Playwright versions with the root version ([#25381](getsentry/sentry-javascript#25381)) - test(e2e): Cover Vercel AI decisions in node-openai-decisions-send-to-sentry ([#25458](getsentry/sentry-javascript#25458)) - test(e2e): Drop OpenRouter's \[DONE] frame in the Anthropic test app ([#25594](getsentry/sentry-javascript#25594)) - test(e2e): Drop unused [@sentry/bundler-plugins](https://github.com/sentry/bundler-plugins) dependency from bundler apps ([#25399](getsentry/sentry-javascript#25399)) - test(e2e): Fix peer dependency issues in hydrogen-react-router-7 ([#25400](getsentry/sentry-javascript#25400)) - test(e2e): Install test-utils from a tarball ([#25402](getsentry/sentry-javascript#25402)) - test(e2e): Move app port 38787 out of the ephemeral port range ([#25504](getsentry/sentry-javascript#25504)) - test(e2e): Remove event dumps and their normalization script ([#25404](getsentry/sentry-javascript#25404)) - test(e2e): Retry tests in all dev-mode variants ([#25640](getsentry/sentry-javascript#25640)) - test(e2e): Use nitro beta and Vite 8 in tanstackstart apps ([#25451](getsentry/sentry-javascript#25451)) - test(nestjs): Fix flaky schedule instrumentation error tests ([#25447](getsentry/sentry-javascript#25447)) - test(nextjs): Bump nextjs-16 E2E app to Next.js 16.4.2 ([#25686](getsentry/sentry-javascript#25686)) - test(nextjs): Fix flaky nextjs-16 metrics tests ([#25517](getsentry/sentry-javascript#25517)) - test(nextjs): Use React 19.3.1 in the vinext e2e variants ([#25449](getsentry/sentry-javascript#25449)) - test(nextjs): Warm the module graph before the tunnel route tests ([#25593](getsentry/sentry-javascript#25593)) - test(node): skip the Prisma 8 suite on Node 20 ([#25421](getsentry/sentry-javascript#25421)) - test(nuxt): Pin the nuxt-4 e2e MongoDB image to 8.0 ([#25557](getsentry/sentry-javascript#25557)) - test(nuxt): Pin the nuxt-5 e2e MongoDB image to 8.0 ([#25564](getsentry/sentry-javascript#25564)) - test(nuxt): Wait for hydration before clicking in error tests ([#25520](getsentry/sentry-javascript#25520)) - test(react): Fix flaky react-router-6 aborted SSE console assertion ([#25398](getsentry/sentry-javascript#25398)) - test(replay): Fix flaky bufferStalledRequests segmentId assertion ([#25394](getsentry/sentry-javascript#25394)) </details> Work in this release was contributed by [@4ktLuffy](https://github.com/4ktLuffy), [@adityareddy-dev](https://github.com/adityareddy-dev), [@dasilvaluis](https://github.com/dasilvaluis), [@faizansaiyed123](https://github.com/faizansaiyed123), [@jpdefo](https://github.com/jpdefo), [@Jxxunnn](https://github.com/Jxxunnn), [@mikamikasuki](https://github.com/mikamikasuki), [@philipatkinson](https://github.com/philipatkinson), [@rubas](https://github.com/rubas), and [@Shubham-Padkonde](https://github.com/Shubham-Padkonde). Thank you for your contributions! - **feat(bun): Add incoming request options and request sessions to `bunServerIntegration`** `bunServerIntegration` now accepts the same options as `denoServeIntegration`: `ignoreRequestBody`, `ignoreIncomingRequests`, `ignoreStaticAssets`, `spans`, `onSpanCreated`, `onSpanEnd`, `sessions` and `sessionFlushingDelayMS`. The callbacks receive the web `Request`. `Bun.serve` now records a request session for each incoming request. Sessions are sent only when a `release` is set. To turn them off, set `bunServerIntegration({ sessions: false })`. `ignoreStaticAssets` defaults to `true`, so `Bun.serve` no longer creates spans for `GET` requests to common static assets such as `favicon.ico`, `robots.txt` or `*.js` files. To keep these spans, set `bunServerIntegration({ ignoreStaticAssets: false })`. `Bun.serve` spans also follow the client's tracing configuration by default, so the integration does not start spans when tracing is disabled. Errors thrown for `OPTIONS` and `HEAD` requests are now captured. - **feat(node): Add `onSpanEnd` to `httpIntegration`** `httpIntegration` and `httpServerSpansIntegration` now accept `onSpanEnd`, a hook that runs when the response for an incoming request finishes, before its span ends. Use it to change the span based on the response. Deno and Bun already have this option. - **feat(bun): Inject debug IDs and upload source maps in `sentryBunPlugin` ([#25670](getsentry/sentry-javascript#25670 `sentryBunPlugin` from `@sentry/bun/plugin` now accepts the same options as `sentryEsbuildPlugin` (`org`, `project`, `authToken`, `release`, `sourcemaps`, ...). When `Bun.build` writes source maps to `outdir`, the plugin injects the debug ID that Bun writes into each bundle, injects the release, and uploads the source maps at the end of the build. You no longer need to run `sentry sourcemap inject` and `sentry sourcemap upload` after the build. Like the other bundler plugins, `sentryBunPlugin` now sends build telemetry and injects the release it detects (for example, from git). To turn off telemetry, set `telemetry: false`.

s1gr1d added 5 commits October 13, 2026 17:28

Merge branch 'develop' into sig/e2e-pnpm-12

2da7679

fix CI failures

b4f49bd

Merge branch 'develop' into sig/e2e-pnpm-12

dad0c87

fix CI failures

8d75018

s1gr1d marked this pull request as ready for review October 14, 2026 10:26

JPeer264 mentioned this pull request Oct 14, 2026

chore: Move the monorepo from Yarn 1 to pnpm 12 #25354

Merged

s1gr1d requested review from JPeer264 and mydea October 14, 2026 11:17

fix other next.js tests

29ae346

mydea reviewed Oct 14, 2026

View reviewed changes

Comment thread dev-packages/bundler-plugin-integration-tests/fixtures/esbuild/package.json Outdated

mydea reviewed Oct 14, 2026

View reviewed changes

Comment thread dev-packages/e2e-tests/test-applications/aws-serverless-layer/package.json Outdated

s1gr1d mentioned this pull request Oct 14, 2026

test(e2e): Inherit root Volta config in all e2e test apps #25369

Merged

JPeer264 added this pull request to stack #25387 October 15, 2026 08:47

s1gr1d added 2 commits October 15, 2026 12:53

fix comment

2c7f5cd

JPeer264 approved these changes Oct 15, 2026

View reviewed changes

review suggestions

abc991b

s1gr1d merged commit 1c5303c into develop Oct 15, 2026
1096 of 1103 checks passed

s1gr1d deleted the sig/e2e-pnpm-12 branch October 15, 2026 14:24

mydea mentioned this pull request Oct 15, 2026

ci(e2e): Run E2E tests without restoring the monorepo's node_modules #25403

Merged

s1gr1d mentioned this pull request Oct 16, 2026

test(e2e): Use nitro beta and Vite 8 in tanstackstart apps #25451

Merged

sentry-release-bot Bot mentioned this pull request Oct 22, 2026

publish: getsentry/sentry-javascript@11.9.0 getsentry/publish#9980

Closed

51 tasks done

	# The devDependency is the one pnpm version for CI and local runs. An app that needs another version sets
	# The dev dependency is the one pnpm version for CI and local runs. An app that needs another version sets

Conversation

s1gr1d commented Oct 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mydea commented Oct 14, 2026

Uh oh!

Uh oh!

JPeer264 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

s1gr1d commented Oct 13, 2026 •

edited

Loading