chore: release.sh takes patch, minor or major
CI / Checks (pull_request) Successful in 36s
PR title / Conventional title (pull_request) Successful in 1s

scripts/release.sh minor bumps the latest release (pre-releases left
out) and says which it bumped; a tag is still taken as it is. Tags are
fetched before the version is worked out.
This commit is contained in:
keb committed 2026-10-15 16:12:20 +02:00
1 parent b3a3c59159
commit e750073afd
2 files changed
+34 -10

No files matched your search

+6 -2
View File
@@ -49,10 +49,14 @@ what its pull request tested, and CI doesn't run again there.
Merge as many pull requests as you like, then release `main`:
```sh
scripts/release.sh --dry-run v0.2.0 # the notes the release would have
scripts/release.sh v0.2.0 # CHANGELOG.md, commit, tag, push
scripts/release.sh --dry-run minor # the tag and notes the release would have
scripts/release.sh minor # CHANGELOG.md, commit, tag, push
```
`patch`, `minor` and `major` bump the latest release (`v0.2.1` → `v0.2.2`,
`v0.3.0`, `v1.0.0`; pre-releases don't count); a tag (`v0.3.0`,
`v0.3.0-rc.1`) is taken as it is.
It refuses unless you're on a clean `main` that matches `origin/main`.
[git-cliff](https://git-cliff.org) (`cliff.toml`) writes `CHANGELOG.md`
from the pull request titles. The tag runs the release workflow