Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/catch-up-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ on:

jobs:
catch-up:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
permissions:
contents: write
pull-requests: write
Expand Down
12 changes: 6 additions & 6 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ on:

jobs:
lint-and-typecheck:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v4

Expand Down Expand Up @@ -48,7 +48,7 @@ jobs:
run: node --test scripts/sync-package-readme.test.mjs

unit-tests:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
needs: lint-and-typecheck
steps:
- uses: actions/checkout@v4
Expand All @@ -72,7 +72,7 @@ jobs:
run: pnpm test

redis-integration:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
needs: lint-and-typecheck
# The package's real-Redis suite (src/integration/*.redis.test.ts). It stops, pauses and
# restarts the server itself, so Redis is a named `docker run` container, not a service.
Expand Down Expand Up @@ -125,7 +125,7 @@ jobs:
run: docker logs "$CACHE_TEST_REDIS_CONTAINER" || true

e2e-tests:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
needs: unit-tests
# Every lane is a production build (`next build` + `next start`) wired with `withCache`.
# The Redis lanes run Redis as a named container (not a service) so the outage spec can stop
Expand Down Expand Up @@ -257,7 +257,7 @@ jobs:
if-no-files-found: ignore

e2e-elasticache:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
needs: unit-tests
# Exercises the ElastiCache handler against the two things that actually differ from a
# plain Redis container on a real cluster: in-transit TLS and an auth token. No AWS is
Expand Down Expand Up @@ -357,7 +357,7 @@ jobs:
if-no-files-found: ignore

test-summary:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
needs: [lint-and-typecheck, unit-tests, e2e-tests, e2e-elasticache, redis-integration]
if: always()
steps:
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/multi-pod-e2e.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ permissions:
jobs:
multi-pod:
name: Multi-pod (${{ matrix.storage }}, ${{ matrix.control }})
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
timeout-minutes: 10
strategy:
fail-fast: false
Expand Down
10 changes: 5 additions & 5 deletions .github/workflows/next-deploy-tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ jobs:
# dependency, which the Next update loops bump), unless a dispatch names another tag.
next-ref:
name: Resolve the next.js tag
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
outputs:
ref: ${{ steps.ref.outputs.ref }}
steps:
Expand All @@ -79,7 +79,7 @@ jobs:
build-nextjs:
name: Build next.js ${{ needs.next-ref.outputs.ref }}
needs: next-ref
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
env:
NEXT_REF: ${{ needs.next-ref.outputs.ref }}
timeout-minutes: 60
Expand Down Expand Up @@ -118,7 +118,7 @@ jobs:

prepare-branch:
name: Pack this branch's package
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
outputs:
skip_reason: ${{ steps.gate.outputs.skip_reason }}
steps:
Expand Down Expand Up @@ -169,7 +169,7 @@ jobs:
suites:
name: ${{ matrix.variant }} (shard ${{ matrix.shard }}/4)
needs: [next-ref, build-nextjs, prepare-branch]
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
timeout-minutes: 75
strategy:
fail-fast: false
Expand Down Expand Up @@ -275,7 +275,7 @@ jobs:
name: Results and regression gate
needs: [next-ref, suites]
if: always() && needs.suites.result != 'skipped'
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
env:
NEXT_REF: ${{ needs.next-ref.outputs.ref }}
steps:
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/nextjs-canary-test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ on:

jobs:
test-canary:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
strategy:
fail-fast: false
matrix:
Expand Down Expand Up @@ -148,7 +148,7 @@ jobs:
echo "✅ All tests passed against Next.js ${{ matrix.nextjs-version }}"

create-issue-on-canary-failure:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
needs: test-canary
if: failure() && github.event_name == 'schedule'
permissions:
Expand Down
4 changes: 2 additions & 2 deletions .github/workflows/nextjs-version-check.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ jobs:
# Fails (and emails the owner) when a tagged release never reached npm, so a
# broken publish chain can't go unnoticed behind an already-merged PR again.
npm-publish-drift:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
steps:
- name: Checkout repository
uses: actions/checkout@v4
Expand All @@ -31,7 +31,7 @@ jobs:
fi

check-nextjs-version:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
permissions:
contents: write
pull-requests: write
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/pr-reminders.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ jobs:
stale-sweep:
# Plain shell, no AI: weekly @-mention for PRs stuck on the maintainer, and
# a gentle check-in on PRs stuck on the contributor.
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
env:
GH_TOKEN: ${{ github.token }}
steps:
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/publish.yml
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ on:

jobs:
publish:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04
# Note: For full automation, we've removed the environment approval requirement
# If you want manual approval, uncomment the next line and configure the "publish" environment in GitHub
# environment: publish
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/tag-on-version-merge.yml
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ jobs:
create-tag:
# Trigger on version-bump/, nextjs-, or catch-up- branches
if: github.event.pull_request.merged == true && (startsWith(github.event.pull_request.head.ref, 'version-bump/') || startsWith(github.event.pull_request.head.ref, 'nextjs-') || startsWith(github.event.pull_request.head.ref, 'catch-up-'))
runs-on: ubuntu-latest
runs-on: ubuntu-24.04

steps:
- name: Checkout repository
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/version-bump.yml
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ permissions:

jobs:
bump-version:
runs-on: ubuntu-latest
runs-on: ubuntu-24.04

steps:
- name: Checkout repository
Expand Down
9 changes: 9 additions & 0 deletions implementation/DECISIONS.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,15 @@
> or "the 16.5 path" is the legacy `createCacheHandler` data stack and the `redis: RedisOptions`
> form. The headings of DEC-1 and DEC-2 keep the numbers those releases had.

## DEC-17: CI runs on `ubuntu-24.04`, not `ubuntu-latest`

On 31 Oct 2026 `ubuntu-latest` moved to Ubuntu 26.04, and the locked Playwright (1.56.1) refuses
to install Chromium there (`Playwright does not support chromium on ubuntu26.04-x64`). The daily
canary test failed from 31 Oct and the daily Next.js version check from 3 Nov, so Next 16.4.4 got
no version bump. Every job now names `ubuntu-24.04`, so a runner image change can no longer stop
the release loop unannounced. Move to a newer image deliberately, with a Playwright that supports
it, in one PR that CI proves.

## DEC-16: Opt-in Redis storage for plain `"use cache"`

Restore `withCache`'s `useCache: "memory" | "redis"` with `"memory"` as the default. This
Expand Down
Loading