I fixed this to ship upstack packages. I reviewed changes here and past versioning changes. I did not notice any other problems.

I also built a test application. It's a .NETFramework application that multi-targets to every supported version of .NETFramework.

I then run dotnet add package Id --prerelease for every package we build in maintenance packages with a feed to my locally built packages. This picks the latest from nuget / local build.

I then build this and look at the generated bindingRedirects to ensure none are required on any framework.

Here's my test if you'd like to try it.
testMP.zip

We might want to integrate something like this into the build.

Note that it must use packages, because the versioning problem only exists when combining things we already published with those built locally. If we just look at build output it will never require redirects.