From cc13b39d379355f42ce6ea0d95f8dbfe5f1d118f Mon Sep 17 00:00:00 2001
From: Sabine Maennel <5292683+sabinem@users.noreply.github.com>
Date: Mon, 28 Sep 2026 08:03:13 +0200
Subject: [PATCH 1/2] docs(releasing): name the bump default, and how to undo
 one

---
 RELEASING.md | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/RELEASING.md b/RELEASING.md
index a15ffb3d..89410b01 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -117,7 +117,7 @@ From an up-to-date, clean `main`:
 
 ```bash
 just version::check           # the versions already agree
-just version::bump minor      # or patch / major
+just version::bump minor      # patch / minor / major — always say which
 git show                      # read the release commit before it leaves
 git push && git push origin v0.9.0
 ```
@@ -127,10 +127,23 @@ commits as `chore(release): v0.9.0` and creates the annotated tag. It pushes
 nothing — it prints the two `git push` commands so the release is never a side
 effect of running it.
 
+Name the bump every time. With no argument `bump` defaults to a `patch`
+and the first place it tells you which one it chose is the commit it has already made.
+
 Pushing the tag builds and pushes `release/backend-service:0.9.0` and
 `release/frontend-service:0.9.0`. A release image is never overwritten, so a
 botched tag is fixed by bumping again, not by re-tagging.
 
+### If you bumped the wrong way
+
+`bump` commits and tags locally and pushes nothing, so a release you have not
+pushed yet is thrown away without anybody else learning of it:
+
+```bash
+git reset --hard origin/main
+git tag -d v0.9.0
+```
+
 If `main` has moved past something you cannot ship and a released version needs
 a fix, branch from the tag rather than from `main`:
 

From 06e90e4274f49ca42efaeeb25fd99310e1ebb641 Mon Sep 17 00:00:00 2001
From: Sabine Maennel <5292683+sabinem@users.noreply.github.com>
Date: Mon, 28 Sep 2026 08:27:52 +0200
Subject: [PATCH 2/2] chore: fix formating

---
 RELEASING.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/RELEASING.md b/RELEASING.md
index 89410b01..02771f55 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -127,8 +127,8 @@ commits as `chore(release): v0.9.0` and creates the annotated tag. It pushes
 nothing — it prints the two `git push` commands so the release is never a side
 effect of running it.
 
-Name the bump every time. With no argument `bump` defaults to a `patch`
-and the first place it tells you which one it chose is the commit it has already made.
+Name the bump every time. With no argument `bump` defaults to a `patch` and the
+first place it tells you which one it chose is the commit it has already made.
 
 Pushing the tag builds and pushes `release/backend-service:0.9.0` and
 `release/frontend-service:0.9.0`. A release image is never overwritten, so a