test(v9/e2e): Fix stale e2e test apps and only test Next.js 15 - #24793
Merged
Merged
Conversation
v9 does not support Next.js 16, but the optional latest and canary e2e variants install next@latest and next@canary, which now resolve to 16. Pin latest to next@15 and drop the canary variants since there is no Next.js 15 canary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
size-limit report 📦
|
Several test apps float on ranges that now resolve to releases requiring Node 22 or newer peers than the ones they pin. Pin them 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. Route the @sentry scope to the test registry. Drop geist from nextjs-t3 since its OFL-1.1 license fails the license check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chargome
changed the title
chargome
marked this pull request as ready for review
September 28, 2026 16:41
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.
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.
latestvariants now installnext@15, and the canary variants are removed. v9 does not support Next.js 16, and there are no Next.js 15 canaries anymore.@opentelemetry/apion TS 3.8, MCP SDK/zod, remix-oxygen, astro) are pinned to the versions that were current around the last v9 release..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@sentryscope because@sentry-internal/node-cpu-profileris only on npm.geistis dropped from nextjs-t3 because its OFL-1.1 license fails the license check.developalready did the same.The optional send-to-sentry jobs still fail because transactions can no longer be looked up by event ID.
developmoved 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.