From 7bcf2cc30ef436c5b289619272ee07815909b428 Mon Sep 17 00:00:00 2001 From: Chrison Simtian Date: Fri, 29 May 2026 18:48:46 +1200 Subject: [PATCH] chore(versioning): add release/v11 to publicReleaseRefSpec (#275) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per NB.GV validation (#275 finding), release/v11 was producing git-sha-suffixed versions like `11.0.19-g4b19a8c1` instead of clean `11.0.19` because the branch wasn't in `publicReleaseRefSpec`. With #274 about to make tag-triggered releases fire from this branch, the suffix would land on nuget.org under what looks like a clean v11.0.X tag — confusing for consumers and not what the tag implies. Adds `^refs/heads/release/v11$` to publicReleaseRefSpec. This branch now produces clean version strings on commits + tag heights. Lands directly on release/v11 (not main) because: - main is still 11.0 and adding release/v11 to main's publicReleaseRefSpec would create a height collision (both branches public-mapped to the same version). - The setting is intentionally branch-specific to how release/v11 generates versions — not something that needs to propagate forward to main / future release/v12. main's publicReleaseRefSpec is unchanged. When #271 lands and bumps main to 12.0, the equivalent edit will happen on release/v12 (or whatever the next major's release branch is named). Refs #275, milestone #13. Co-Authored-By: Claude Opus 4.7 (1M context) --- version.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/version.json b/version.json index 37cce9c1b..d0fd8b5f6 100644 --- a/version.json +++ b/version.json @@ -2,7 +2,8 @@ "$schema": "https://raw.githubusercontent.com/dotnet/Nerdbank.GitVersioning/main/src/NerdBank.GitVersioning/version.schema.json", "version": "11.0", "publicReleaseRefSpec": [ - "^refs/heads/main$" + "^refs/heads/main$", + "^refs/heads/release/v11$" ], "pathFilters": [ ":/",