semrel
Go tool that automates semantic releases by computing SemVer from commits and publishing versions.
Tested on Linux
Use it
Linux x86_64
Download versioned semrel tarball and inspect
curl -sSL -o /tmp/semrel.tar.gz https://github.com/SemRels/semrel/releases/download/v0.28.3/semrel_0.28.3_linux_amd64.tar.gz && mkdir -p ~/.local/binInstall semrel binary to local bin
mkdir -p /tmp/sx2 && tar -xzf /tmp/semrel.tar.gz -C /tmp/sx2 && cp /tmp/sx2/semrel ~/.local/bin/semrel && chmod +x ~/.local/bin/semrel && semrel --version
Where the README and reality differ
- README: curl -sSL https://github.com/SemRels/semrel/releases/latest/download/semrel_linux_amd64.tar.gz | tar -xz semrel + sudo mv
What worked: download versioned asset https://github.com/SemRels/semrel/releases/download/v0.28.3/semrel_0.28.3_linux_amd64.tar.gz (assets are per-version), extract in an empty dir and copy semrel to ~/.local/bin (no sudo) - README: semrel release --dry-run with zero side effects after semrel config init
What worked: replace default plugins with minimal core-only .semrel.yaml (plugins: []) before offline dry-run; default config auto-installs condition-github-actions and fails its condition check outside GitHub Actions
Check that it works
semrel --versionThe output should contain “semrel version v0.28.3+dirty”.
First thing to try
rm -rf /tmp/demorepo && mkdir -p /tmp/demorepo && cd /tmp/demorepo && git init -q && git config user.email "test@example.com" && git config user.name "Test" && echo "# demo" > README.md && git add README.md && GIT_AUTHOR_DATE="2024-01-01T00:00:00Z" GIT_COMMITTER_DATE="2024-01-01T00:00:00Z" git commit -qm "feat: initial feature" && echo "change" >> README.md && git add README.md && GIT_AUTHOR_DATE="2024-01-02T00:00:00Z" GIT_COMMITTER_DATE="2024-01-02T00:00:00Z" git commit -qm "fix: a bug fix" && semrel config init && cat .semrel.yamlcd /tmp/demorepo && git branch -M main && semrel doctorInside a Git repository, run semrel doctor to check your setup, then semrel config init to create a .semrel.yaml config file.
What it does
- Work out the next SemVer version from commitsTested
How to use it
- In your Git repository, run
semrel config initto create.semrel.yaml, and set your branch and bump rules (for example feat to minor, fix to patch). - Run
semrel release --dry-runto see the next version without releasing.
- In your Git repository, run
- Generate Keep-a-Changelog release notesTested
How to use it
- In a repository with a
.semrel.yamlconfig, runsemrel changelog.
- In a repository with a
- Update version manifests across language ecosystemsNot tested
- Create releases on Git forgesNot tested
How far pickfit got
Linux x86_64
- Installs
- Starts
- 2 of 4 features work
- Works offline
macOS and Windows: the project says it runs there; pickfit hasn’t tried it.
Good for
- compute next SemVer version from Conventional Commits
- generate Keep-a-Changelog release notes
- validate commits against Conventional Commits
An alternative to semantic-release, GoReleaser, release-please, release-it and changesets.
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version v0.28.3+dirty