HubSpot developer CLI needs Node.js 22 or later from 8 January 2027

HubSpot developer CLI needs Node.js 22 or later from 8 January 2027

19 October 2026: HubSpot will stop supporting Node.js 20 in its developer CLI on 8 January 2027, after which the CLI "will require Node.js v22 or higher to run". Anyone who builds HubSpot CMS themes, UI extensions or app projects with the CLI, on a laptop or in a pipeline, needs a newer runtime before that date.

Not yet independently verified. Rests on HubSpot's own changelog; the release date of the updated HubSpot GitHub Action is not yet stated. We will update this when it can be confirmed, and remove this note.

What HubSpot is changing

The changelog entry, posted on 19 October, ties the move to Node.js 20 reaching end of life on 30 April 2026, six months ago. HubSpot notes that while Node.js is largely backward compatible, compatibility "is not guaranteed", and that running older CLI versions on Node.js 20 may bring compatibility issues or breaking changes. The upgrade path it gives is a newer Node.js and then the latest CLI with npm i -g @hubspot/cli@latest.

Users of the HubSpot GitHub Action are in a slightly different position: they will need to move to the latest action version "once released" to get Node.js 22 support, and HubSpot has not said when that version ships. Pipelines pinned to an older action tag will keep running on whatever runtime the tag declares until someone changes it.

Why Node.js 22 is a short stop

HubSpot's floor is Node.js 22, but the Node.js release schedule puts Node.js 22 at end of life on 30 April 2027, less than four months after HubSpot's cutoff. Node.js 24 entered maintenance on 20 October 2026 and is supported until 30 April 2028, and Node.js 26 becomes the active LTS line on 28 October 2026 with support to 30 April 2029. A team changing its CI images for this deadline saves itself a second change in spring by moving to 24 or 26 now, provided its other build tools support them.

Where to look in a build

The Node.js version a HubSpot project actually uses is often set in more than one place: an .nvmrc or engines field in package.json, the node-version input of a setup step in GitHub Actions, a base image in a Dockerfile, and whatever is installed on a developer's machine. The CLI checks the runtime it is started with, so a pipeline can fail after 8 January even where every laptop has been upgraded. HubSpot is in our CRM software category, which lists 6 products.

Related on TrustList:

• HubSpot ends design manager serverless functions on 1 February 2027
• Brotli fixes a critical decoder flaw that reaches far beyond Node.js

Sources

• HubSpot Developer Changelog: Upcoming sunset, end of developer CLI support of Node.js 20, 19 October 2026
• Node.js Release Working Group: release schedule (read 2026-10-20), 20 October 2026