Plugins
Official plugins
@semantic-release/commit-analyzer
Note: this is already part of semantic-release and does not have to be installed separately
analyzeCommits
: Determine the type of release by analyzing commits with conventional-changelog
@semantic-release/release-notes-generator
Note: this is already part of semantic-release and does not have to be installed separately
generateNotes
: Generate release notes for the commits added since the last release with conventional-changelog
Note: this is already part of semantic-release and does not have to be installed separately
verifyConditions
: Verify the presence and the validity of the GitHub authentication and release configurationpublish
: Publish a GitHub releasesuccess
: Add a comment to GitHub issues and pull requests resolved in the releasefail
: Open a GitHub issue when a release fails
Note: this is already part of semantic-release and does not have to be installed separately
verifyConditions
: Verify the presence and the validity of the npm authentication and release configurationprepare
: Update the package.json version and create the npm package tarballpublish
: Publish the package on the npm registry
verifyConditions
: Verify the presence and the validity of the GitLab authentication and release configurationpublish
: Publish a GitLab release
verifyConditions
: Verify the presence and the validity of the Git authentication and release configurationprepare
: Push a release commit and tag, including configurable files
verifyConditions
: Verify the presence and the validity of the configurationprepare
: Create or update the changelog file in the local project repository
verifyConditions
: Execute a shell command to verify if the release should happenanalyzeCommits
: Execute a shell command to determine the type of releaseverifyRelease
: Execute a shell command to verifying a release that was determined before and is about to be publishedgenerateNotes
: Execute a shell command to generate the release noteprepare
: Execute a shell command to prepare the releasepublish
: Execute a shell command to publish the releasesuccess
: Execute a shell command to notify of a new releasefail
: Execute a shell command to notify of a failed release
verifyConditions
: Verify the presence of theATOM_ACCESS_TOKEN
environment variable and theapm
CLIprepare
: Update thepackage.json
version withnpm version
publish
: Publish the Atom package
Community plugins
Open a Pull Request to add your plugin to the list.
verifyConditions
: Verify that the environment variableSLACK_WEBHOOK
has been defined.success
: Publish a message about the success to a slack channel.fail
: Optionally publish a message about failure to a slack channel.
verifyConditions
: Verify that all needed configuration is present and login to the Docker registry.publish
: Tag the image specified byname
with the new version, push it to Docker Hub and update the latest tag
verifyConditions
: Verify that all needed configuration is present and login to the Docker registrypublish
: Tag the image specified byname
with the new version, push it to Docker Hub and update the latest tag
verifyConditions
: Verify the presence and the validity of the vsce authentication and release configurationprepare
: Create a.vsix
for distributionpublish
: Publish the package to the Visual Studio Code marketplace
verifyConditions
: Check the dependencies format against a regexp before a release
verifyConditions
: Verify the presence of the authentication (set via environment variables)prepare
: Write the correct version to themanifest.json
and creates a zip file of the whole dist folderpublish
: Uploads the generated zip file to the webstore, and publish the item
semantic-release-firefox-add-on
verifyConditions
: Verify that all required options are present and authentication is set via environment variablesprepare
: Write the correct version to themanifest.json
publish
: Creates an unsigned.xpi
file, and submits it to the Mozilla Add On store for signing. Once the package is signed, downloads the signed.xpi
to a local directory
generateNotes
: Generate release notes with Gerrit reviews URL
verifyConditions
: Verify Expo manifest(s) are readable and valid.prepare
: Update version, ios build number and android version code in the Expo manifest(s).
verifyConditions
: Verifies that thepom.xml
file and other files exist and are setup to allow releasesverifyRelease
: Checks and warns (does not error by default) if the version numbers found on maven central and within the Git project differ by quite a bitprepare
: Changes the version number in thepom.xml
(or allpom.xml
files in maven projects with multiplepom.xml
files) and optionally creates a commit with this version number and pushes it tomaster
publish
: Runsmvn deploy
to deploy to maven central and optionally will update to next snapshot version and merge changes to development branch
prepare
: Stores the version number as an Azure DevOps pipeline variable availabe to downstream steps on the job
verifyConditions
: Verify that project has a Gradle wrapper script, andbuild.gradle
contains a task to publish artifacts.prepare
: Changes the version number in thegradle.properties
publish
: Triggers Gradle to publish artifacts.
verifyConditions
: Verify the presence of theCIRCLECI_API_TOKEN
environment variable,orbName
option, and thecircleci
CLI.publish
: Publish the CircleCI orb.
verifyConditions
: Verify the presence of the auth token set via environment variables.publish
: Pushes commit to the documentation branch.
verifyConditions
: Checks the project.clj is syntactically valid.prepare
: Update the project.clj version and package the output jar file.publish
: Publish the jar (and generated Maven metadata) to a maven repository (or clojars).
@saithodev/semantic-release-gitea
verifyConditions
: Verify the presence and the validity of the authentication and the assets option configuration.publish
: Publish a Gitea release, optionally uploading file assets.addChannel
: Update a Gitea release's pre-release field.
Last updated