Skip to content

fix(e2e): pin Next.js version in cache-components template#8121

Open
jacekradko wants to merge 5 commits intomainfrom
jacek/pin-nextjs-version-cache-components
Open

fix(e2e): pin Next.js version in cache-components template#8121
jacekradko wants to merge 5 commits intomainfrom
jacek/pin-nextjs-version-cache-components

Conversation

@jacekradko
Copy link
Member

@jacekradko jacekradko commented Mar 19, 2026

Summary

  • Pin Next.js in the cache-components integration test template from ^16.0.0-canary.0 to 16.1.6

The cache-components test suite has been deterministically failing since March 18, not flaky. Root cause:

  • The template had "next": "^16.0.0-canary.0" with no lockfile, so every CI run resolved the latest compatible version
  • Next.js 16.2.0 was published on 2026-03-18 at 17:17 UTC
  • Every CI run after that picked up 16.2.0, which breaks window.Clerk?.session initialization after sign-in
  • The last passing run (March 14) used Next.js 16.1.6
  • All "passing" runs between March 14–18 were Turbo cache hits that never actually executed tests

This pins to 16.1.6 to unblock CI. The 16.2.0 incompatibility should be investigated separately.

Test plan

  • Integration Tests (cache-components, chrome, 16) passes in CI

Summary by CodeRabbit

  • Chores
    • Updated Next.js to a stable release version for improved stability and reliability.

Next.js 16.2.0 (released 2026-03-18) breaks Clerk session initialization
in the cache-components test app, causing waitForSession to timeout.
Pin to 16.1.6 (last known working version) to unblock CI.
@changeset-bot
Copy link

changeset-bot bot commented Mar 19, 2026

🦋 Changeset detected

Latest commit: be6de6b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link

vercel bot commented Mar 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
clerk-js-sandbox Ready Ready Preview, Comment Mar 20, 2026 1:48am

Request Review

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 19, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: dcf87cab-ed4c-4124-95cc-7837c61c8637

📥 Commits

Reviewing files that changed from the base of the PR and between e00ec97 and 2e6fd4d.

📒 Files selected for processing (2)
  • .changeset/pin-nextjs-cache-components.md
  • integration/templates/next-cache-components/package.json

📝 Walkthrough

Walkthrough

A changeset entry was created to document changes to the Next.js cache components template. The next dependency in integration/templates/next-cache-components/package.json was updated from a canary version (^16.0.0-canary.0) to a stable pinned release version (16.1.6). This change transitions the template's Next.js dependency from using a flexible canary range to a fixed, released version.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: pinning the Next.js version in the cache-components template from a canary range to a stable version (16.1.6) to fix failing e2e tests.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

📝 Coding Plan
  • Generate coding plan for human review comments

Comment @coderabbitai help to get the list of available commands and usage tips.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Mar 19, 2026

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@8121

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8121

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8121

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8121

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8121

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@8121

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8121

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8121

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8121

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8121

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8121

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8121

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8121

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8121

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8121

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8121

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8121

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8121

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8121

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8121

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8121

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8121

commit: be6de6b

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant