GitLab CI
Last updated
Last updated
The environment variables can be configured with .
Note: Make sure to configure your release branch as in order for the CI/CD build to access the protected variables.
Since GitLab CI is a for , it is recommended to enable this to increase supply-chain security for your npm packages. Find more detail about configuring npm to publish with provenance through semantic-release .
GitLab CI supports allowing to test on multiple Node versions and publishing a release only when all test pass.
Note: The publish pipeline must run a .
.gitlab-ci.yml
configuration for Node projectsThis example is a minimal configuration for semantic-release with a build running Node 10 and 12. See for additional configuration options.
Note: Thesemantic-release
execution command varies depending on whether you are using a or semantic-release installation.
.gitlab-ci.yml
configuration for all projectspackage.json
configurationThis example is a minimal configuration for semantic-release with a build running Node 10 and 12. See for additional configuration options.
Note: Thesemantic-release
execution command varies depending if you are using a or semantic-release installation.
A package.json
is required only for semantic-release installation.