Repository navigation
chore: Raise the Node engines floor to 24 - #43
Merged
Merged
Conversation
Strapi Cloud is the CMS host and Node 24 is the version we accept there, so the engines range no longer needs to admit Node 22. CI built only on the .nvmrc Node 26, so nothing proved the floor actually works. Key changes: - engines.node is >=24.0.0 <=26.x.x in package.json and the lockfile - CI also installs and builds on Node 24, failing if the Node it runs is not 24
|
|
ecv
enabled auto-merge
November 5, 2026 01:31
andrewb3000
approved these changes
Nov 5, 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.
The CMS's
enginesrange still admitted Node 22, which loses upstream support in April 2027. Strapi Cloud hosts the CMS, and Node 24 is the version we accept there, so the floor moves to 24. Images and CI stay on Node 26 via.nvmrc.Until now CI only built on Node 26, so nothing showed the CMS actually installs and builds on the floor version. The required check now does both.
Changes
engines.nodeis>=24.0.0 <=26.x.xinpackage.jsonandpackage-lock.json.npm ciandnpm run buildon Node 24, and fails if the Node it runs is not 24.Not covered here
.npmrcsets noengine-strict, so if Strapi Cloud still runs Node 22, npm only warns at install and the deploy does not fail. Someone with Strapi Cloud access should confirm it is on Node 24.Related to #34
Related to https://github.com/datum-cloud/infra/issues/8215