From 450f0341fd6e7ea510893cd15defebb5de3ac985 Mon Sep 17 00:00:00 2001 From: Samantha Coyle Date: Tue, 19 May 2026 13:57:45 -0500 Subject: [PATCH 1/2] chore: bump main version ref too now Signed-off-by: Samantha Coyle --- VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VERSION b/VERSION index 4773ce83..42e7d7a0 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -1.18.0.dev \ No newline at end of file +1.19.0.dev \ No newline at end of file From 25ba4359d5c5683303ecbc7e6606902a2ef62534 Mon Sep 17 00:00:00 2001 From: Samantha Coyle Date: Tue, 19 May 2026 14:53:26 -0500 Subject: [PATCH 2/2] style: update docs so we dont always have to bump those too for releases Signed-off-by: Samantha Coyle --- RELEASE.md | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index d5922f7a..c3fe5476 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -53,12 +53,17 @@ the packages. Each package's `pyproject.toml` reads from it. | Stage | `VERSION` example | | ---------------------------------- | ----------------------------- | -| Development (always on `main`) | `1.18.0.dev` | -| First RC (on `release-X.Y`) | `1.18.0rc0` | -| Subsequent RCs (on `release-X.Y`) | `1.18.0rc1`, `1.18.0rc2`, … | -| Stable release | `1.18.0` | -| Patch release candidate | `1.18.1rc1` | -| Stable patch release | `1.18.1` | +| Development (always on `main`) | `X.Y.0.dev` | +| First RC (on `release-X.Y`) | `X.Y.0rc0` | +| Subsequent RCs (on `release-X.Y`) | `X.Y.0rc1`, `X.Y.0rc2`, … | +| Stable release | `X.Y.0` | +| Patch release candidate | `X.Y.1rc1` | +| Stable patch release | `X.Y.1` | + +`X.Y` is the major.minor of the release line you're working on (the branch +name `release-X.Y` matches). `main` always carries the **next** un-released +minor as `.dev` — once `release-X.Y` is forked, `main` advances from +`X.Y.0.dev` to the next minor's `.dev` (e.g. `X.(Y+1).0.dev`). ## Remote convention