Upgrade runtime and framework majors - #1255
Merged
Merged
Conversation
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
1 participant
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.
Summary of changes
Upgrades the application to Node 24, pnpm 11, Next.js 16, React 19, TypeScript 7, Tinykeys 4, and the latest major GitHub Actions. Migrates the Next.js middleware convention to
proxy, moves pnpm security overrides and build permissions topnpm-workspace.yaml, and updates the narrow React 19 and TypeScript 7 compatibility points.Next.js uses the TypeScript 7 CLI integration and now enforces type checking during production builds. Frozen installation, dependency audit, clean type generation, Turbopack production build, sitemap generation, development/production HTTP checks, and desktop/mobile browser interactions all pass.
Docs
Local and CI development now require Node 24 and pnpm 11.