Skip to content

v3.0.0-rc9

v3.0.0-rc9: release: PlatformVersion 3.0.0-rc8 → 3.0.0-rc9 (#2834)
@rbuergi rbuergi tagged this 30 Aug 20:22 
Cuts the next pre-release line so `dotnet tool install -g MeshWeaver.Cli`
carries `memex build plugin` (#2832) — the CLI is packed from this repo
(IsPackable=true) and release-packages.yml publishes on a `v*.*.*` tag, which
`v3.0.0-rc9` matches.

🚨 HOLD: this must land AFTER #2832. An rc cut before it would publish a tool
without the verb it exists to deliver.

Verified rather than assumed:
 - the computed version is right: `dotnet msbuild -getProperty:Version
   -p:CIRun=true` → 3.0.0-rc9.ci.35653 (the .ci.<n> suffix still derives from
   the run number, so CI builds stay monotonic on the new line);
 - the -rc label is KEPT, which the props file explains is not cosmetic:
   pre-release identifiers compare ASCII-lexically, "ci" < "preview1", so a
   bare 3.0.0 core would sort every CI build BELOW the published
   v3.0.0-preview1 and the self-updater would pin there for ever;
 - five test files mention 3.0.0-rc8 and NONE of them pins PlatformVersion —
   all five are fixture literals or a doc comment (ReleaseFactTest compares
   two identical literals; FrameworkReleaseBroadcasterTest feeds one in and
   asserts it back; DockerImageGateArgsTest is a const image string;
   ViewerZoneTimestampTest is a fixture value; CdImageVersionsShareOneSource-
   Guard is prose). Checked each rather than trusting the grep count.

Previous line: rc3, rc5, rc6, rc7, rc8 — so rc9 is next.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Assets 2
Loading