chore(tools): complete 10.3 contaminated-version unlist batch (10.3.24-47) - #294
Merged
Conversation
…4-47) The original unlist-10.3.40-47.json (#224) only covered the 10.3.40-47 tail and missed 10.3.24-39 — including the entire System.Text.Json breaking migration (ef83796, #171), which is patch zero of the contamination. Adds unlist-10.3.24-47.json: the complete 256-entry batch covering every published 10.3.x >= 10.3.24 across all 18 package IDs. Boundary is exact — 10.3.23 (commit 44770a6, #170) is the last clean patch and is where release/v10.3 is now parked. Keeps the old 40-47 file as the historical record of what was first identified; README documents both and the boundary. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisonSimtian
enabled auto-merge (squash)
May 29, 2026 08:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Completes the record of which
10.3.xversions carry v11 breaking changes, so they can be unlisted from nuget.org.Why
The existing
unlist-10.3.40-47.json(#224) is incomplete. It only covered10.3.40–10.3.47(the CLI-rename tail) — 102 entries. But the contamination starts much earlier.The boundary (exact)
version.jsonwent to10.3at #107; Nerdbank git-height maps 1:1 to the published patch number (no offset, no pathFilters on the 10.3 line). So:10.3.2344770a6a(#170) — whererelease/v10.3is now parked10.3.24ef837961(#171) —feat(text.json)!drop Newtonsoft / STJ migrationEverything
≥ 10.3.24shipped breaking changes under a10.3label before the v11 semver-policy fix (#220, #222).What this adds
tools/unlist-10.3.24-47.json— complete 256-entry batch, every published10.3.x ≥ .24across all 18 package IDs (built from live nuget.org data, so only versions that actually exist).unlist-10.3.40-47.jsonas the historical record (per maintainer call); README documents both + the boundary.Published contaminated patches:
.24 .25 .26 .27 .28 .29 .36 .37 .38 .40 .41 .42 .44 .45 .47(×17 pkgs) +.39(Fallout.Cli only). Gaps (.30–.35,.43,.46) never published.Tooling/record only — no build or pipeline impact (
tools/is pathFilter-excluded from versioning). The actual unlist + a clean10.3.48marker are the operational follow-up.🤖 Generated with Claude Code