[tillig]

Phase 3h. Small, but it revises one decision from the plan.

Release notes list

Rather than reading down the list, I checked every repository it links against the GitHub API:

• Autofac.Extras.MvvmCross is archived — entry removed. The other 23 are active.
• Comparing the list against the set of shipping packages turned up exactly one omission: Autofac.Pooling, now listed under extended features.

A plan revision: 8.x does need an upgrade page

The approved plan said to add "a short note that 8.0 and 9.0 were TFM-only rather than new upgrade-guide pages." That was right about 9.0 and wrong about 8.0.

ResolveRequest went from a class to a readonly struct:

public readonly struct ResolveRequest : IEquatable<ResolveRequest>

That's a compile break, not a target-framework change. Comparing one to null stops working, and it's copied by value now, so a method taking one can't mutate the caller's copy. The affected audience — custom resolve middleware and custom IInstanceActivator implementations — is exactly who the 5-to-6 page was written for, which is what convinced me it deserves the same treatment.

The page also records the 8.4.0 change making the shim RequiresUnreferencedCodeAttribute internal (verified: it's internal sealed class in LinkerAttributes.cs, and the commit making it so is in history).

8.x to 9.x now has a page too

Added on review feedback, and the reasoning is better than mine was: leaving it out puts a hole in the series, which reads as an oversight rather than as "nothing happened" — and it would look stranger still once a 9-to-10 page sits next to a missing 8-to-9. The sentence in the 7-to-8 page explaining why there was no 8-to-9 page is removed accordingly.

Upgrade pages are the one place target-framework changes belong — it's what the 6-to-7 page does for net5.0 — so this one leads with them. Checked against the project files rather than the release notes:

	Target frameworks
8.4.0	net8.0;net7.0;net6.0;netstandard2.1;netstandard2.0
9.x	net10.0;net8.0;netstandard2.1;netstandard2.0

So net6.0 and net7.0 dropped, net10.0 added. Applications still on net6.0/net7.0 can consume the release through netstandard2.1 — the same framing the 6-to-7 page used for net5.0.

The dependency bumps are the part with real consequences, since they flow transitively and raise the floor for consuming applications. I read the conditions off the csproj so the page says which targets each affects rather than implying both apply everywhere:

• System.Diagnostics.DiagnosticSource 8.0.1 → 10.0.0, on every target
• Microsoft.Bcl.AsyncInterfaces 8.0.0 → 10.0.0, on netstandard2.0 only

A closing section points at what 9.x added — AnyKey and [ServiceKey], opt-in metrics, trimming and AOT annotations — so the page is worth opening even though the upgrade itself asks nothing of you.

Verification

sphinx -W, doc8, pre-commit, npm run lint clean. Nested-markup and bad-link scans clean. Confirmed the new page uses the overline-plus-underline title convention established in #197, and that the whats-new toctree renders in the right order with the new page ahead of 6-to-7.

Note on sequencing

This is independent of the outstanding stub work. owners.rst and support.rst still need reducing to stubs, but that has to wait for autofac/.github#2 to merge — the stubs link to MAINTAINERS.md, which doesn't exist on main yet, and I'd rather not ship a PR that knowingly introduces a 404.