mirror of
https://github.com/chatmail/core.git
synced 2026-04-17 21:46:35 +03:00
4026c827be
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 :)
22 lines
944 B
Markdown
22 lines
944 B
Markdown
# Releasing a new version of DeltaChat core
|
|
|
|
For example, to release version 1.116.0 of the core, do the following steps.
|
|
|
|
1. Resolve all [blocker issues](https://github.com/deltachat/deltachat-core-rust/labels/blocker).
|
|
|
|
2. Update the changelog: `git cliff --unreleased --tag 1.116.0 --prepend CHANGELOG.md` or `git cliff -u -t 1.116.0 -p CHANGELOG.md`.
|
|
|
|
3. 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`
|
|
|
|
4. Update the version by running `scripts/set_core_version.py 1.116.0`.
|
|
|
|
5. Commit the changes as `chore(release): prepare for 1.116.0`.
|
|
Optionally, use a separate branch like `prep-1.116.0` for this commit and open a PR for review.
|
|
|
|
6. Tag the release: `git tag --annotate v1.116.0`.
|
|
|
|
7. Push the release tag: `git push origin v1.116.0`.
|
|
|
|
8. Create a GitHub release: `gh release create v1.116.0 --notes ''`.
|