Skip to content

Commit 4e5b4cd

Browse files
committed
no-mistakes(document): docs: fix RELEASING.md main-only release claims
1 parent b829e49 commit 4e5b4cd

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

‎docs/RELEASING.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,9 @@ Publish in tier order so a dependent never lands before its dependency. **`forge
186186
released. `v0.24.5` carries exactly that, and nothing caught it because no page
187187
displayed a coordinate yet.
188188

189-
So `release.mjs` pushes `main` and **stops**. After the ports are bumped, committed,
189+
So `release.mjs` pushes the branch it runs on (`main`, or a `release/<major>.<minor>`
190+
maintenance branch — see the maintenance-branch section below) and **stops**. After the
191+
ports are bumped, committed,
190192
pushed and tagged (`python-v*`, `csharp-v*`, `java-v<npm major + 7>.*` — `java-v8.*` at the
191193
1.0 cut, NOT `java-v7.*`), run:
192194

@@ -733,7 +735,9 @@ lock the repo/owner IDs against resurrection attacks.)
733735
734736
## Procedure
735737
736-
1. **Pick the publish commit on `main`** (a stable, merged tip — not a mid-refactor branch). Ensure
738+
1. **Pick the publish commit on the branch the release is cut from** (`main`, or the
739+
`release/<major>.<minor>` maintenance branch for a patch — the workflow publishes the
740+
COMMITTED `<Version>`, so the tag must name that branch's tree). Ensure
737741
the packaging config + `publish-csharp.yml` are on it. Set `<Version>` in `Directory.Build.props`.
738742
2. **Validate locally** (catches immutable-version mistakes before they're permanent):
739743
```bash

0 commit comments

Comments
 (0)