Repository navigation
chore: Build the CMS on Node 26 - #39
Merged
Merged
Conversation
Move CI to Node 26, the current LTS line, and let the engines range admit it. Strapi 5.59 already supports Node 20 through 26. Key features/changes: - better-sqlite3 11.3.0 fails to compile on Node 26, whose V8 drops Object::GetPrototype; 12.11.1 ships a Node 26 prebuild - .nvmrc moves to 26, so CI builds on it - engines widens to 26 and keeps the 22.19 floor, so a host still on Node 22 or 24 keeps deploying On Node 22 and Node 26, npm ci, lint and the production build pass, and a started server answers /_health 204 and /admin 200, matching main.
3 tasks
andrewb3000
approved these changes
Nov 1, 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
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
The CMS builds on Node 22, two LTS lines behind the Node 26 line the fleet is moving to.
On Node 26 the install fails, because the pinned SQLite driver no longer compiles against Node 26. This moves CI to Node 26 and bumps that driver to a release that ships a Node 26 build.
The engines range widens to admit Node 26 and keeps its Node 22 floor, so the hosted CMS keeps deploying whichever Node line its host runs.
Test plan
Related to #34