Problem
docs/migration/from-nuke.md:102 tells consumers, as a caveat on the transition-shim path:
The shim is a transition aid, not a permanent home. It's removed in 12.0. Plan to migrate before then.
There is no 12.0 and there will not be one. The 11.x line was skipped and the project moved from 10.x straight to calendar versioning (ADR-0004); the stray 11.0.x packages on nuget.org are unlisted. So the single deadline consumers are given for the shim's removal names a version that will never ship — in the page the FALLOUT004 diagnostic's help link points at, which is the page someone reads precisely when deciding whether the shim is safe to sit on.
Found while removing docs/rebrand-plan.md in #591. The same claim was in src/Fallout.Migrate.Analyzers/README.md ("ship through the 11.x line, remove in 12.0") and is fixed there; #591 was kept scoped to the doc removal, so the consumer-facing copy is still live.
Outcome
The migration guide states the shim's removal in terms that stay true as the version line moves: it is a breaking change, so it lands at a yearly major cut, and it is undated until that cut is chosen. A consumer reading it can tell whether they have to act now, without being given a fake deadline.
Acceptance criteria
Notes
Related but out of scope: whether the shim moves off GitHub Packages to drop the PAT requirement (#344), and the incomplete shim surface (#69) — both already have their own caveats on that page.
Problem
docs/migration/from-nuke.md:102tells consumers, as a caveat on the transition-shim path:There is no 12.0 and there will not be one. The
11.xline was skipped and the project moved from10.xstraight to calendar versioning (ADR-0004); the stray11.0.xpackages on nuget.org are unlisted. So the single deadline consumers are given for the shim's removal names a version that will never ship — in the page theFALLOUT004diagnostic's help link points at, which is the page someone reads precisely when deciding whether the shim is safe to sit on.Found while removing
docs/rebrand-plan.mdin #591. The same claim was insrc/Fallout.Migrate.Analyzers/README.md("ship through the 11.x line, remove in 12.0") and is fixed there; #591 was kept scoped to the doc removal, so the consumer-facing copy is still live.Outcome
The migration guide states the shim's removal in terms that stay true as the version line moves: it is a breaking change, so it lands at a yearly major cut, and it is undated until that cut is chosen. A consumer reading it can tell whether they have to act now, without being given a fake deadline.
Acceptance criteria
docs/migration/from-nuke.mdno longer references12.0.Notes
Related but out of scope: whether the shim moves off GitHub Packages to drop the PAT requirement (#344), and the incomplete shim surface (#69) — both already have their own caveats on that page.