From abf0ebf41d7d41439acdc9578f506a54a633e799 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Tue, 7 Sep 2021 13:01:36 +0200 Subject: [PATCH] docs: process for releasing --- README.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README.md b/README.md index cfb311d1..3700b15c 100644 --- a/README.md +++ b/README.md @@ -58,6 +58,15 @@ We use [goreleaser](https://goreleaser.com) to help us automate releases. We use For developers, while using this `-alpha` format, the `y` part is the "major" version part. So, if you make breaking changes, you increment that and _not_ the `x` part. So, if you're on `0.1.0-alpha`, then you'd go to `0.1.1-alpha` for a backwards compatible change and `0.2.0-alpha` for a backwards incompatible change. +## Making a new release + +- Change `ABRA_VERSION` to match the new tag in [`scripts`](./scripts/installer/installer) (use [semver](https://semver.org)) +- Commit that change (e.g. `git commit -m 'chore: publish next tag 0.3.1-alpha'`) +- Make a new tag (e.g. `git tag 0.y.z-alpha`) +- Push the new tag (e.g. `git push && git push --tags`) +- Wait until the build finishes on [build.coopcloud.tech](https://build.coopcloud.tech/coop-cloud/abra) +- Check the release worked, (e.g. `abra upgrade; abra version`) + ## Fork maintenance We maintain a fork of [godotenv](https://github.com/Autonomic-Cooperative/godotenv) for two features: