generateNotes
: Generate release notes for the commits added since the last release with conventional-changelog​verifyConditions
: Verify the presence and the validity of the GitHub authentication and release configurationsuccess
: Add a comment to GitHub issues and pull requests resolved in the releasefail
: Open a GitHub issue when a release failsverifyConditions
: 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 registryverifyConditions
: Verify the presence and the validity of the GitLab authentication and release configurationverifyConditions
: Verify the presence and the validity of the Git authentication and release configurationprepare
: Push a release commit and tag, including configurable filesverifyConditions
: Verify the presence and the validity of the configurationprepare
: Create or update the changelog file in the local project repositoryverifyConditions
: 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 releaseverifyConditions
: Verify that the environment variable SLACK_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 by name
with the new version, push it to Docker Hub and update the latest tagverifyConditions
: Verify that all needed configuration is present and login to the configured docker registry.publish
: Tag the image specified by name
with the new version and channel and push it to the configured docker registry.addChannel
: Updates a release published on one channel with the destinations channel tag and pushes to the registry ie: next to latest.verifyConditions
: Verify that all needed configuration is present and login to the Docker registrypublish
: Tag the image specified by name
with the new version, push it to Docker Hub and update the latest tagverifyConditions
: 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 marketplaceverifyConditions
: Check the dependencies format against a regexp before a releaseverifyConditions
: Verify the presence of the authentication (set via environment variables)prepare
: Write the correct version to the manifest.json
and creates a zip file of the whole dist folderpublish
: Uploads the generated zip file to the webstore, and publish the itemverifyConditions
: Verify that all required options are present and authentication is set via environment variablesprepare
: Write the correct version to the manifest.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 directorygenerateNotes
: Generate release notes with Gerrit reviews URLverifyConditions
: 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 the pom.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 the pom.xml
(or all pom.xml
files in maven projects with multiple pom.xml
files) and optionally creates a commit with this version number and pushes it to master
publish
: Runs mvn deploy
to deploy to maven central and optionally will update to next snapshot version and merge changes to development branchprepare
: Stores the version number as an Azure DevOps pipeline variable availabe to downstream steps on the jobverifyConditions
: Verify that project has a Gradle wrapper script, and build.gradle
contains a task to publish artifacts.prepare
: Changes the version number in the gradle.properties
publish
: Triggers Gradle to publish artifacts.verifyConditions
: Verify the presence of the CIRCLECI_API_TOKEN
environment variable, orbName
option, and the circleci
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
: Verify the presence and the validity of the GitHub authentication and other configuration.publish
: Create a branch to upload all assets and create the pull request on the base branch on GitHub.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).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.prepare
: Replace version strings in files using regex and glob.verifyConditions
: Locate and validate a .gemspec
file, locate and validate a lib/**/version.rb
file, verify the presence of the GEM_HOST_API_KEY
environment variable, and create a credentials file with the API key.verifyConditions
: Validates configuration.publish
: Deprecates old versions, based on the declaration of supported versions in the config.verifyConditions
: Verify the presence and the validity of the npm authentication and release configuration for multiple registriesprepare
: Update the package.json version and create the npm package tarballpublish
: Publish the package on the npm registry for multiple registriesverifyConditions
: Verify the presence of a license fileprepare
: Update the license file based on its typeverifyConditions
: Verify the environment variable PYPI_TOKEN
and installation of build toolsprepare
: Update the version in setup.cfg
and create the distribution packagespublish
: Publish the python package to a repository (default: pypi)verifyConditions
: Validate configuration and (if present) credentialsprepare
: Update version and appVersion in Chart.yaml
publish
: Publish the chart to a registry (if configured)verifyConditions
: Validate configuration, get AWS CodeArtifact authentication and repository, validate publishConfig
or .npmrc
(if they exist), then pass the configuration to the associated plugins.verifyConditions
: Validate configuration and verify TELEGRAM_BOT_ID
and TELEGRAM_BOT_TOKEN
success
: Publish a message about the successful release to a telegram chatfail
: publish a message about failure to a telegram chatverifyConditions
: Validate configuration and verify HEROKU_API_KEY
prepare
: Update the package.json version and create release tarballpublish
: Publish version to herokuverifyConditions
: Verify that the webhook is setup and release-notes-generator is present.verifyConditions
: Verify github tokens are present and valid.verifyRelease
: Display information regarding the matching github milestone.verifyConditions
: Validate configuration and verify TELEGRAM_BOT_TOKEN
and package namesuccess
: Publish a success message to certain telegram chatsfail
: Publish a fail message to certain telegram chatspublish
: Automatically mark old versions as deprecated.verifyConditions
: Verify plugin configuration and login to Helm registryprepare
: Package Helm chart to local folderpublish
: Publish Helm chart to OCI registry