10 guides · synced daily from GitHub
releaser docs
semantic-release without the plugins, the config or node_modules. Conventional commits in; version, changelog, tag and GitHub release out. One static Go binary.
Getting started
Add the action and ship your first release.
Getting Started
Release on every push to main, straight from your commit messages. No config file, no plugins.
Inputs and flags
Every action input maps to a CLI flag of the same name.
Migrating from semantic-release
Delete .releaserc.json, the plugins in package.json and the npx semantic-release step. Each plugin maps to built-in behavior or one input.
Releasing
How versions are picked and what gets published.
Release flows
Two inputs pick how releases reach main. Neither is the default.
Versioning
Commit format. Rules. Tags. Release notes.
Artifact mode
Attach build outputs to the GitHub release.
Docker mode
Build ./Dockerfile and push it tagged with the release version.
Canaries and release PR
For trunk-based development: every push to main ships a canary, and a release PR carries the next stable version. Merging the PR releases it.
Internals
How the code fits together.