HubSpot CLI is dropping Node.js 20: what to do before 8 January 2027

Based on HubSpot's announcement of 19 October 2026. Check the HubSpot developer changelog for any updates.

HubSpot has announced that its developer CLI will stop supporting Node.js 20. From 8 January 2027, the CLI requires Node.js 22 or later. If you build HubSpot themes, modules or projects on your own machine, or deploy them from a CI pipeline, it's worth checking your setup now rather than finding out when a deploy fails.

What's changing

• Node.js 22 becomes the minimum. HubSpot is deprecating Node.js 20 from the developer CLI starting on 8 January 2027, and the CLI will need Node.js v22 or higher.
• Old setups may break. HubSpot says Node.js is largely backward compatible, but that compatibility isn't guaranteed, and running older CLI versions on Node.js 20 may cause compatibility issues or breaking changes.
• GitHub Actions need an update too. If you deploy with HubSpot's GitHub Action, HubSpot asks you to move to its latest version, once released, to support Node.js 22 and later.

The reason is simple: Node.js 20 reached its end of life on 30 April 2026, so it no longer receives security fixes. Tools built on it have to move on.

Who it affects

Anyone who uses the HubSpot CLI (the hs command), which typically means:

• Developers building or editing HubSpot CMS themes and modules locally, then uploading them.
• Teams building HubSpot apps and projects that are developed and deployed with the CLI.
• Automated pipelines, such as GitHub Actions or other CI systems, that upload or deploy to HubSpot.
• Freelancers and agencies working on clients' HubSpot accounts from their own machines.

If your team only edits pages, emails and content in HubSpot's own editor in the browser, nothing changes for you.

Which Node.js version to choose

Node.js 22 meets HubSpot's minimum, but it isn't a long-term home: according to the Node.js release schedule, Node.js 22 reaches its own end of life on 30 April 2027, only a few months after HubSpot's deadline. HubSpot's requirement is "22 or higher", so many teams will prefer to move straight to Node.js 24, which is supported until April 2028, and avoid doing this twice. Node.js 26 is also scheduled to become a long-term support release on 28 October 2026, with support until April 2029. Whichever you pick, test your build with it before the deadline.

Key dates

How to upgrade

1. 1Check what you're running. Run node -v on every machine and in every pipeline that uses the CLI.
2. 2Install a newer Node.js. A version manager such as nvm, fnm or Volta makes it easy to switch, and lets each project use the version it needs.
3. 3Pin the version in the project. Add an .nvmrc file or an engines entry in package.json, so everyone on the team, and your CI, uses the same version.
4. 4Update the CLI. HubSpot recommends upgrading to the latest version with npm i -g @hubspot/cli@latest, then confirm it with hs --version.
5. 5Test your usual workflow. Run the commands you rely on, such as fetching, uploading and watching files or deploying a project, ideally against a sandbox or developer account first.
6. 6Update your pipelines. Change the Node.js version in your CI configuration (for example node-version in GitHub's setup-node step), and switch to HubSpot's updated GitHub Action when it's released.
7. 7Tell your collaborators. Freelancers, agencies and anyone else who deploys to your HubSpot account need to upgrade too.

A quick checklist

• Every developer machine on Node.js 22 or later (24 if you want more runway).
• The latest HubSpot CLI installed everywhere.
• Project Node.js version pinned in the repository.
• CI pipelines and the HubSpot GitHub Action updated.
• A test upload or deploy done before the deadline.

Sources: HubSpot developer changelog, HubSpot community discussion and the Node.js release schedule.