Skip to content

[Bug]: Central package management breaks no-op restores #11696

@marcin-krystianc

Description

@marcin-krystianc

NuGet Product Used

dotnet.exe

Product Version

dotnet 6.0.100

Worked before?

dotnet 5.0.100

Impact

It bothers me. A fix would be nice

Repro Steps & Context

  1. Checkout project that uses central package management, e.g.: NoOpIssue.zip

  2. Run dotnet restore twice.

  3. The second restore should be no-op restore ("All projects are up-to-date for restore." in the command output), but it is not the case for dotnet 6.0.100

Verbose Logs

d:\workspace\TestSolutions\NoOpIssue\App>dotnet --version
6.0.100

d:\workspace\TestSolutions\NoOpIssue\App>dotnet restore
  Determining projects to restore...
  The project d:\workspace\TestSolutions\NoOpIssue\App\App.csproj is using CentralPackageVersionManagement, a NuGet preview feature.
  Restored d:\workspace\TestSolutions\NoOpIssue\App\App.csproj (in 187 ms).

d:\workspace\TestSolutions\NoOpIssue\App>dotnet restore
  Determining projects to restore...
  The project d:\workspace\TestSolutions\NoOpIssue\App\App.csproj is using CentralPackageVersionManagement, a NuGet preview feature.
  Restored d:\workspace\TestSolutions\NoOpIssue\App\App.csproj (in 161 ms).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions