Skip to content

Introduction

simple-release-action runs the whole release flow in your CI: on every push to the main branch it creates or updates a release pull request with the version bump and changelog, and when that pull request is merged, it tags, publishes, and creates the GitHub release.

Setting it up takes two files — a config describing the project and a release workflow. The action reads the addon query from the config and installs the addons itself, so your repository needs no extra dependencies. See Release Automation for the full setup.

The workflow input selects what the action does in the current job:

WorkflowDescription
fullDetect the context and run the pull request or release flow. The default.
checkDetermine which workflow should run and skip unnecessary runs — used as the first job.
pull-requestCreate or update the release pull request.
releaseTag, publish, and create the release — runs on the release commit.
snapshotPublish a temporary snapshot version.
InputDescription
workflowWorkflow to run. Defaults to full.
github-tokenGitHub token to authenticate with the GitHub API. Required.
npm-tokennpm token for publishing. Passed to the NODE_AUTH_TOKEN environment variable.
publish-tokenGeneric token for the config file. Passed to the PUBLISH_TOKEN environment variable.
branchBranch to store release changes and create the pull request from. Defaults to simple-release.
bump-versionForce a specific version.
bump-asForce a release type: major, minor, patch, or prerelease.
bump-prereleasePre-release identifier, e.g. alpha or beta.
bump-snapshotSnapshot pre-release identifier.
bump-first-releaseTreat the current version as the first release. Auto-detected by default.
bump-skipSkip the version bump.
bump-by-projectJSON object with per-project bump options for monorepos.
maintenance-branchCreate maintenance branches for previous major versions.
publish-skipSkip publishing.
publish-accessPackage access level: public or restricted.
publish-tagnpm tag for the publication.