chore(tools): commit unlist-10.3.40-47.json batch as historical record#224
Merged
Merged
Conversation
102-entry bulk-input for Unlist-NugetPackage.ps1, covering the 10.3.40-10.3.47 range across all 17 affected Fallout.* packages. These are the patch versions that shipped breaking changes before the v11 semver-policy fix in #220 — keeping the batch under source control so the cleanup is reproducible / auditable. Also amends tools/README.md to point at this file as the live example of an "operation worth keeping as a historical record."
This was referenced May 27, 2026
ChrisonSimtian
added a commit
that referenced
this pull request
May 29, 2026
…4-47) (#294) 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>
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
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.
Summary
Drops the 102-entry bulk-input file alongside the script that consumes it, so the actual cleanup is reproducible / auditable from source.
`tools/unlist-10.3.40-47.json` — JSON array of `{ package, version }` covering the `10.3.40`-`10.3.47` range across all 17 affected `Fallout.*` packages. These are the patch versions that shipped breaking changes before the v11 semver-policy fix in #220.
To run the cleanup:
```
pwsh ./tools/Unlist-NugetPackage.ps1 -JsonPath ./tools/unlist-10.3.40-47.json
```
(API key from `-ApiKey` or `$env:NUGET_API_KEY`.)
Also amends `tools/README.md`: the existing line about "operations worth keeping as a historical record" now points at this file as the live example.
Test plan