GitHub Action for Conventional Commit repos

Always-ready draft releases.

SAVR updates release notes on every push so your team can publish manually from the GitHub Releases page when ready.

View on GitHub See the quick start
  • No forced auto-publish
  • No manual release workflow to trigger
  • Publish from the GitHub Releases UI
Release workflow
  1. Push commits `feat`, `fix`, and breaking changes update the next version.
  2. SAVR updates the draft Release notes stay current on every push to your release branch.
  3. Publish in GitHub Your team reviews the draft and ships from the Releases page. 
jobs:
  release:
    steps:
      - uses: actions/checkout@v5
        with:
          fetch-depth: 0
      - uses: 21stdigital/savr-action@v2
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}

Why teams pick SAVR

Prepared automatically. Published deliberately.

Better than auto-publish when review matters

Fully automated tools are great when you want releases to ship themselves. SAVR is for teams that want the release prepared continuously but still want a human to decide when it goes live.

Better than manual workflow dispatch when friction matters

Some teams keep manual control by triggering a release workflow. SAVR removes that extra step by keeping the release draft ready inside GitHub itself.

Narrow by design

SAVR focuses on release preparation. It does not try to own package publishing, changelog files, or every release concern in your CI pipeline.

Comparison

Choose the workflow that matches your release process.

Approach Best when
Fully automated release tools You want CI to publish releases without human review.
Manual release workflows You are comfortable triggering a release job each time someone cuts a release.
SAVR You want the release prepared continuously and published manually from the GitHub Releases UI.

Fit check

Use it when the release draft itself is the workflow.

Use SAVR if

  • You already use Conventional Commits
  • You want the next release visible before it ships
  • You want to publish directly from GitHub
  • You want manual control without manual release jobs

Skip SAVR if

  • You want end-to-end automated package publishing
  • You need changelog files managed automatically
  • You do not want Conventional Commits
  • You are happy with a `workflow_dispatch` release process