semantic-release
AboutGitHubNeed Help?
next
next
  • Introduction
  • Usage
    • Getting started
    • Installation
    • CI Configuration
    • Configuration
    • Plugins
    • Workflow configuration
    • Shareable configurations
  • Extending
    • Plugins
    • Shareable configuration
  • Recipes
    • CI configurations
      • CircleCI 2.0
      • Travis CI
      • GitLab CI
    • Git hosted services
      • Git authentication with SSH keys
    • Package managers and languages
  • Developer guide
    • JavaScript API
    • Plugin development
    • Shareable configuration development
  • Support
    • Resources
    • Frequently Asked Questions
    • Troubleshooting
    • Node version requirement
    • Node Support Policy
Powered by GitBook
On this page
  • Recommended solution
  • Run at least one CI job with Node >= 10.18
  • Alternative solutions
  • Use npx
  • Use nvm
Edit on Git
  1. Support

Node version requirement

PreviousTroubleshootingNextNode Support Policy

Last updated 5 years ago

semantic-release is written using the latest features, without transpilation which requires requires Node version 10 or higher.

semantic-release is meant to be used in a CI environment as a development support tool, not as a production dependency. Therefore the only constraint is to run the semantic-release in a CI environment providing Node 8 or higher.

See our for our long-term promise regarding Node version support.

Recommended solution

Run at least one CI job with Node >= 10.18

The recommended approach is to run the semantic-release command from a CI job running on Node 10.18 or higher. This can either be a job used by your project to test on Node >= 10.18 or a dedicated job for the release steps.

See and for more details.

Alternative solutions

Use npx

npx is included with npm >= 5.2 and can be used to download the latest . Use it to execute the semantic-release command.

$ npx -p node@8 -c "npx semantic-release"

Note:: See for more details.

Use nvm

$ nvm install 8 && npx semantic-release

If your CI environment provides you can use it to switch to Node 8 before running the semantic-release command.

nvm
ECMAScript 2017
Node Support Policy
CI configuration
Node 8 package published on npm
CI configuration recipes
What is npx