fix(v9/nextjs): Align tunnel request matching in middleware with tunnel rewrite - #24760
Merged
Merged
Conversation
…el rewrite Backport of: #24499
Contributor
size-limit report 📦
|
chargome
added a commit
that referenced
this pull request
Sep 28, 2026
v9 CI had gone red for reasons unrelated to the changes being tested (see #24760): dependency ranges in the e2e test apps kept floating to newer releases. - Next.js `latest` variants now install `next@15`, and the canary variants are removed. v9 does not support Next.js 16, and there are no Next.js 15 canaries anymore. - Test apps whose deps drifted to releases that need Node 22 (nuxt via cssnano 8, wrangler) or that no longer fit the other pinned versions (pg-protocol types, `@opentelemetry/api` on TS 3.8, MCP SDK/zod, remix-oxygen, astro) are pinned to the versions that were current around the last v9 release. - node-profiling-cjs/esm, cloudflare-astro and cloudflare-hono had no active `.npmrc`, so they installed `@sentry/*` from npm (now v11) instead of the local build. They now use the test registry. The profiling apps only route the `@sentry` scope because `@sentry-internal/node-cpu-profiler` is only on npm. - `geist` is dropped from nextjs-t3 because its OFL-1.1 license fails the license check. `develop` already did the same. The optional send-to-sentry jobs still fail because transactions can no longer be looked up by event ID. `develop` moved those tests to the trace endpoint, and porting that is left for a follow-up. cloudflare-astro builds now but fails when deploying to Cloudflare Pages with an auth error from the Cloudflare API. --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
chargome
marked this pull request as ready for review
September 28, 2026 17:04
nicohrubec
approved these changes
Sep 28, 2026
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
2 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.
Backport of: #24499
Differences to the original PR
packages/nextjs/src/common/utils/tunnelPathnameMatch.ts: this file doesn't exist on v9, so it's added here with onlyisSentryTunnelRequest.isPathnameUnderSentryTunnelRouteis left out because nothing on v9 uses it.pathname.startsWith(tunnelRoute), so a path like/api/thingscounted as a tunnel request for/api/t.developfixed that in an earlier PR. The new exact matching fixes it on v9 too, so the test for that case fromdevelopis included here.