Fallout-migrate triggers some dependency confusion

[dennisdoomen]

Usage Information

Fallout 10.3.45

Description

While upgrading two individual existing Nuke 10 projects, fallout-migrate triggered the following error

Reproduction Steps

Take an existing Nuke project, run fallout-migrate

Expected Behavior

After invoking build.ps1, it should just work out of the box.

Actual Behavior

Microsoft (R) .NET Core SDK version 10.0.204
    C:\Workspaces\fluentassertions\build\_build.csproj : error NU1603: Warning As Error: _build depends on Fallout.Common (>= 10.1.0) but Fallout.Common 10.1.0 was not found. Fallout.Common 10.2.12 was resolved instead.
    C:\Workspaces\fluentassertions\build\_build.csproj : error NU1603: Warning As Error: _build depends on Fallout.Components (>= 10.1.0) but Fallout.Components 10.1.0 was not found. Fallout.Components 10.2.12 was resolved instead.
    C:\Workspaces\fluentassertions\build\_build.csproj : error NU1605:
      Warning As Error: Detected package downgrade: System.Security.Cryptography.Xml from 10.0.6 to 9.0.15. Reference the package directly from the
      project to select a different version.
       _build -> Fallout.Common 10.2.12 -> System.Security.Cryptography.Xml (>= 10.0.6)
       _build -> System.Security.Cryptography.Xml (>= 9.0.15 && < 10.0.0)

Regression?

Unknown

Known Workarounds

Bump Fallout.Common and Fallout.Components to the latest version. Also, I've seen two Nuke-based projects that depended on System.Security.Cryptography.Xml that was causing vulnerability messages. I had to remove that one.

Could you help with a pull-request?

Yes