This is by design.  The source code was not changed between release
and Only the NuGet packages were changed.

I have not seen the issue with Visual Studio using binding redirects before;
however, it seems like an issue specific to Visual Studio, i.e. as far as I
know, there is no requirement for a NuGet package version to exactly match
that of the managed assemblies contained within it.