analyzeCommits: Determine the type of release by analyzing commits with conventional-changeloggenerateNotes: Generate release notes for the commits added since the last release with conventional-changelogverifyConditions: 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 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 configurationpublish: Publish a GitLab releaseverifyConditions: 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 published.generateNotes: 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 releaseOpen a Pull Request to add your plugin to the list.
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 tag.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 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 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 the presence of the authentication (set via environment variables)prepare: Write the correct version to the manifest.json, creates a xpi file of the dist folder and a zip of the sourcespublish: Submit the generated archives to the webstore for review, and publish the item including release notesgenerateNotes: 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).