Move the blog CMS from Node 22 to Node 26 #34

Activity

1. ecv

   assigned

   mattdjenkinson

   on Oct 28, 2026
2. ecv commented on Nov 1, 2026

   

   ecv

   on Nov 1, 2026

   ContributorAuthor

   More actions

   Current Node pins on the default branch, read 2026-11-01: .nvmrc 22, which CI reads, and engines.node >=22.19.0 <=24.x.x.

   Moved in #39. Results in the official Debian trixie images, main on Node 22.23.4 against the pull request on Node 26.13.0:

   Step	main, Node 22	main, Node 26	PR, Node 26
   npm ci	pass	fails	pass
   npm run lint	pass	not reached	pass
   strapi build, production	pass	not reached	pass
   started server: /_health, /admin	204, 200	not reached	204, 200
   /api/users-permissions/roles, /graphql	403, 400	not reached	403, 400

   • On main, npm ci fails on Node 26 because better-sqlite3 11.3.0 compiles from source and Node 26's V8 dropped Object::GetPrototype. The pull request moves it to 12.11.1, which ships a Node 26 prebuild. The pull request also passes on Node 22.
   • Strapi 5.59 declares Node 20 through 26.
   • Source search for APIs removed between Node 22 and 26 found none.
   • The CMS deploys to Strapi Cloud, which picks its Node line from the project settings, not from this repo. The engines range keeps its Node 22 floor so a deploy still on 22 or 24 does not break. Moving the hosted runtime to 26 is a settings change that should follow, once Strapi Cloud offers Node 26. Until then this issue stays open.
3. ecv commented on Nov 1, 2026

   

   ecv

   on Nov 1, 2026

   ContributorAuthor

   More actions

   #39 merged on 1 Nov at 12:05Z, which meets the first criterion. The Strapi Cloud runtime setting is the one item left, once Strapi Cloud offers Node 26.