using long options make things less mystical, it is clearer what happens. (apart from that i also disallowed `git -a` on my machine in general, as `git commit -a` is considered harmful. as my approach to disallow that is a bit greedy and disallows `-a` just for any git commands, this is the only place where i regularly struggle :)
944 B
Releasing a new version of DeltaChat core
For example, to release version 1.116.0 of the core, do the following steps.
-
Resolve all blocker issues.
-
Update the changelog:
git cliff --unreleased --tag 1.116.0 --prepend CHANGELOG.mdorgit cliff -u -t 1.116.0 -p CHANGELOG.md. -
add a link to compare previous with current version to the end of CHANGELOG.md:
[1.116.0]: https://github.com/deltachat/deltachat-core-rust/compare/v1.115.2...v1.116.0 -
Update the version by running
scripts/set_core_version.py 1.116.0. -
Commit the changes as
chore(release): prepare for 1.116.0. Optionally, use a separate branch likeprep-1.116.0for this commit and open a PR for review. -
Tag the release:
git tag --annotate v1.116.0. -
Push the release tag:
git push origin v1.116.0. -
Create a GitHub release:
gh release create v1.116.0 --notes ''.