10.x line follow-ups: protect release/v10, publish 10.3.48 marker, reconcile docs/pipeline #300

Activity

1. ChrisonSimtian

   changed the title [-]Consolidate release/v10.1 + v10.2 + v10.3 into a single 10.x maintenance branch[/-] [+]10.x line follow-ups: protect release/v10, publish 10.3.48 marker, reconcile docs/pipeline[/+] on May 29, 2026
2. ChrisonSimtian commented on May 29, 2026

   

   ChrisonSimtian

   on May 29, 2026

   CollaboratorAuthor

   More actions

   Marker publish is blocked by a Build.cs gate — coupled to the pipeline reconciliation.

   release/v10's (#170-era) Build.cs hard-gates publishing to main:

   • IPublish.Publish → .Requires(() => GitRepository.IsOnMainBranch() && …)
   • ICreateGitHubRelease.CreateGitHubRelease → .OnlyWhenStatic(() => IsOnMainBranch())

   So ./build.cmd Test Pack Publish from release/v10 no-ops at the publish step. This is why #274's new pipeline packs + raw dotnet nuget push instead of using the Publish target.

   To ship the 10.3.x marker (will be 10.3.49 after the config fixup commit bumps git-height), the 10.x line needs one of:

   1. Patch release/v10 Build.cs to allow publishing from release/v* (un-gate IsOnMainBranch), or
   2. Port the new pipeline's pack + raw dotnet nuget push approach to release/v10.

   Plus the already-known config fixup: version.json publicReleaseRefSpec and release.yml push trigger still reference the old release/v10.3 (rename leftovers) → must point at release/v10.
3. ChrisonSimtian

   added

   target/v10

   on Jun 16, 2026
4. ChrisonSimtian

   closed this as not plannedon Jul 11, 2026