A Sample NPM package with automated deployment based on branches to NPM for both release snapshot releases.
- How to setup automated CI/CD for package new or existing project
- How to add new feature or fix
- How to release final version
- How to update type to
module
To skip automated release (CI/CD pipeline), add
[ci skip]
into your git commit message.
Refer to this document.
Pipeline completes, but doesn't release new version saying "This run was triggered by a pull request and therefore a new version won't be published."
When there is a Pull Request open for the branch, CircleCI would consider it as if its run from the PR, so semantic-release would not be able to release the version.
To fix it, just temporary close the PR and trigger the Pipeline again. Once its complete, you can re-open the same PR.
Pipeline completes, but dosn't release new version saying "There are no relevant changes, so no new version is released."
This could happen due to multiple reasons:
- Commit message prefix is not proper. (most common) eg:
fix:START upgrade mwc-radio to latest version
This does not have space after:
- The
feature/*
branch andmaster
branch are at the same point. (e.g there isn't any new commit on feature branch, so there is nothing new)