chore: release.sh takes patch, minor or major (#87)
Co-authored-by: Karl-Einar Bergstrøm <karl-einarb@outlook.com>
This commit was merged in pull request #87.
This commit is contained in:
1 parent
b3a3c59159
commit
27d6251579
2 files changed
+34
-10
No files matched your search
+6
-2
@@ -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
|
||||
|
||||
Reference in new issue
Block a user