Skip to content

Commit f024f39

Browse files
committed
docs: document release process in RELEASE.md
1 parent 24d52c5 commit f024f39

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

RELEASE.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# Releasing a new version of DeltaChat core
2+
3+
For example, to release version 1.116.0 of the core, do the following steps.
4+
5+
1. Resolve all [blocker issues](https://github.com/deltachat/deltachat-core-rust/labels/blocker).
6+
7+
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`.
8+
9+
3. Update the version by running `scripts/set_core_version.py 1.116.0`.
10+
11+
4. Commit the changes as `chore(release): prepare for 1.116.0`.
12+
Optionally, use a separate branch like `prep-1.116.0` for this commit and open a PR for review.
13+
14+
5. Tag the release: `git tag -a v1.116.0`.
15+
16+
6. Push the release tag: `git push origin v1.116.0`.
17+
18+
7. Create a GitHub release: `gh release create v1.116.0 -n ''`.

0 commit comments

Comments
 (0)