- Remove the `getLastRelease` plugin type - Retrieve the last release based on Git tags - Create the next release Git tag before calling the `publish` plugins BREAKING CHANGE: Remove the `getLastRelease` plugin type The `getLastRelease` plugins will not be called anymore. BREAKING CHANGE: Git repository authentication is now mandatory The Git authentication is now mandatory and must be set via `GH_TOKEN`, `GITHUB_TOKEN`, `GL_TOKEN`, `GITLAB_TOKEN` or `GIT_CREDENTIALS` as described in [CI configuration](https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/ci-configuration.md#authentication).
2.6 KiB
2.6 KiB
Plugins list
Default plugins
- @semantic-release/github
- verifyConditions: Verify the presence and the validity of the GitHub authentication and release configuration
- publish: Publish a GitHub release
- @semantic-release/npm
- verifyConditions: Verify the presence and the validity of the npm authentication and release configuration
- publish: Publish the package on the npm registry
Official plugins
- @semantic-release/gitlab
- verifyConditions: Verify the presence and the validity of the GitLab authentication and release configuration
- publish: Publish a GitLab release
- @semantic-release/git
- verifyConditions: Verify the presence and the validity of the Git authentication and release configuration
- publish: Push a release commit and tag, including configurable files
- @semantic-release/changelog
- verifyConditions: Verify the presence and the validity of the configuration
- publish: Create or update the changelog file in the local project repository
- @semantic-release/exec
- verifyConditions: Execute a shell command to verify if the release should happen
- analyzeCommits: Execute a shell command to determine the type of release
- verifyRelease: Execute a shell command to verifying a release that was determined before and is about to be published.
- generateNotes: Execute a shell command to generate the release note
- publish: Execute a shell command to publish the release.