Skip to content

docs(releasing): name the bump default, and how to undo one #318

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sabinem wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs(releasing): name the bump default, and how to undo one #318

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cc13b39
docs(releasing): name the bump default, and how to undo one
sabinem Sep 28, 2026
06e90e4
chore: fix formating
sabinem Sep 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
```
Expand All @@ -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`:

Expand Down
Loading