release: 3.0.0 is cut first, then the line moves to 3.1.0 — PlatformVersion back to 3.0.0 by rbuergi · Pull Request #3366 · Systemorph/MeshWeaver

rbuergi · 2026-09-05T21:15:44Z

Summary

Maintainer, this evening: "let's then release 3.0.0 and then cut to 3.1.0. that was the intention" — "i don't want this rc business any more" — "i want to release it only when we have solved all issues".

PlatformVersion 3.1.0 → 3.0.0. Continuous builds are 3.0.0-ci.<n>; the release is the clean 3.0.0, a promotion of a sealed set (release: the 3.1.0 line — no rc, no NuGet, and a release is a promotion of a sealed set #3354's release.yml, unchanged), cut only once every open issue in Release 3.0.0, then open 3.1.0 (tracking) #3355 is closed; the lane then opens the bump to 3.1.0. No pre-release label anywhere. NuGet stays retired.
Doc/ReleaseNotes/3_1_0 → 3_0_0 (the page describes the 3.x line, which 3.0.0 is); the What's New entry from release: the 3.1.0 line — no rc, no NuGet, and a release is a promotion of a sealed set #3354 is renamed and reworded; ReleaseProcess, ReleaseStrategy, the /release skill and the props comment describe the 3.0.0-first order.

The ordering cost, stated rather than hidden. A 3.0.0-ci.<n> build sorts below the 3.0.0-rc* images already in ACR (SemVer §11.4 compares ci < rc as text), so until the clean 3.0.0 lands a Continuous install on an rc build stays put — never back, never forward. The clean 3.0.0 outranks every rc and is what moves the fleet; after it 3.1.0-ci.<n> resumes rolling. Production is frozen (UpdatePolicy None) anyway. The two 3.1.0-ci sets published while the props briefly read 3.1.0 (7832, 7835) outrank 3.0.0; an install that took one will skip the release and wait for the first 3.1.0-ci build after the bump. Whether to hide those two version tags in ACR is the maintainer's call (digests stay; Plugins pins by digest).

Verification

dotnet msbuild -getProperty:Version: 3.0.0-ci.7900 (CIRun, run 7900), 3.0.0 (PublicRelease); AssemblyVersion 3.0.0.0.
test/MeshWeaver.Documentation.Test -c Release -warnaserror: 0 warnings, 0 errors; 269/269 on an assembly that embeds the renamed What's New entry (link integrity over the moved notes page).
release.yml needs no change: it refuses a tag whose version ≠ PlatformVersion, so v3.0.0 on a commit at 3.0.0 with a 3.0.0-ci.<n> sealed set is exactly what it accepts, and its next-line computation yields 3.1.0.

Plugins is unaffected (pins by digest; its AssemblyVersion follows the platform in hand since #1367).

Pairs-with: none — a version-number change removes no public surface.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JuXoLRvG9TfKh5mgnjGfmo

…ersion back to 3.0.0 Maintainer, evening 2026-09-05: "let's then release 3.0.0 and then cut to 3.1.0. that was the intention" — "i don't want this rc business any more" — "i want to release it only when we have solved all issues". So PlatformVersion goes 3.1.0 → 3.0.0: continuous builds are 3.0.0-ci.<n>, the release is the clean 3.0.0 (a promotion of a sealed set, cut only once every open issue is closed), and the day v3.0.0 is tagged release.yml opens the bump to 3.1.0. No pre-release label anywhere; NuGet stays retired. The ordering cost is stated, not hidden: a 3.0.0-ci.<n> build sorts BELOW the 3.0.0-rc* images already in ACR (SemVer §11.4: "ci" < "rc" as text), so until the clean 3.0.0 lands a Continuous install on an rc build stays put — never back, never forward. The clean 3.0.0 outranks every rc and is what moves the fleet; after it 3.1.0-ci.<n> resumes rolling. The two 3.1.0-ci sets published while the props briefly read 3.1.0 (7832, 7835) outrank 3.0.0: an install that took one skips the release and waits for the first 3.1.0-ci build. Doc/ReleaseNotes/3_1_0 → 3_0_0 (the page describes the 3.x line, which 3.0.0 IS); the What's New entry follows; ReleaseProcess, ReleaseStrategy, the release skill and the props comment describe the 3.0.0-first order and the ordering note. Verified: -getProperty:Version → 3.0.0-ci.7900 (CIRun) / 3.0.0 (PublicRelease); AssemblyVersion 3.0.0.0. MeshWeaver.Documentation.Test -c Release -warnaserror 0/0, 269/269 on an assembly that embeds the renamed entry (link integrity over the moved notes page). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JuXoLRvG9TfKh5mgnjGfmo

Copilot

🟡 Changes recommended

It leaves verified conflicting documentation/workflow references elsewhere in the repo still describing the continuous/release versions as 3.1.0, which makes the versioning guidance inconsistent.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR aligns the platform’s versioning and release documentation with the maintainer decision to cut 3.0.0 first (no rc labels), then open the 3.1.0 line, reverting PlatformVersion from 3.1.0 back to 3.0.0 and updating the release runbooks accordingly.

Changes:

Revert PlatformVersion to 3.0.0 and update the authoritative versioning commentary/ordering notes.
Rename and reword the 3.x “release is a promotion” documentation (What’s New + Release Notes) for the 3.0.0 release.
Update release process/strategy docs and the /release skill to reflect “3.0.0 release → bump to 3.1.0”.

File summaries

File	Description
src/MeshWeaver.Documentation/Data/WhatsNew/2026-09-05-the-3-0-0-release-is-a-promotion.md	Updates the What’s New entry to describe the 3.0.0-first release plan and CI/release tag ordering implications.
src/MeshWeaver.Documentation/Data/ReleaseNotes/3_0_0/index.md	Renames the release notes page to 3.0.0 and updates narrative and upgrade guidance to match the new cut order.
src/MeshWeaver.Documentation/Data/Architecture/ReleaseStrategy.md	Updates release strategy guidance for `PlatformVersion = 3.0.0`, tagging `v3.0.0`, and next-line bump to 3.1.0.
src/MeshWeaver.Documentation/Data/Architecture/ReleaseProcess.md	Reverts the documented `PlatformVersion` snippet and updates the SemVer ordering explanation for 3.0.0-first.
src/MeshWeaver.Documentation/Data/Architecture/AuthoringDocumentation.md	Updates the ReleaseNotes example path to `3_0_0`.
Directory.Build.props	Reverts `PlatformVersion` to `3.0.0` and updates the long-form comment explaining channel ordering and the “no rc” policy.
.claude/skills/release/SKILL.md	Updates the release runbook (continuous vs official) to use `3.0.0-ci.<run#>` / `v3.0.0` and bump to 3.1.0.

Review details

Files reviewed: 7/7 changed files
Comments generated: 1
Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

github-actions · 2026-09-05T21:20:35Z