@marcpopMSFT
When do we expect this one to merge? Is there anything blocking?

@erdembayar This test is failing:

It looks like previously if you tried to run dotnet list package on a project that wasn't restored, it would print an error but return success (0) as the exit code. Now it looks like it's returning a failure. Is this an expected change?

@erdembayar This test is failing:

sdk/src/Tests/dotnet-list-package.Tests/GivenDotnetListPackage.cs

Lines 142 to 156 in 96fc61c

	public void AssetsPathExistsButNotRestored()
	{
	var testAsset = "NewtonSoftDependentProject";
	var projectDirectory = _testAssetsManager
	.CopyTestAsset(testAsset)
	.WithSource()
	.Path;
	new ListPackageCommand(Log)
	.WithWorkingDirectory(projectDirectory)
	.Execute()
	.Should()
	.Pass()
	.And.HaveStdErr();
	}

It looks like previously if you tried to run dotnet list package on a project that wasn't restored, it would print an error but return success (0) as the exit code. Now it looks like it's returning a failure. Is this an expected change?

Yes, it's expected change. We added non-zero exit codes indicate something wrong with the "dotnet list package" report, so customer need to take a look into it.
You can see spec here.

I've updated the test to account for the changed return code.

FYI @dotnet/dotnet-cli, we should probably document this as a breaking change for .NET 8.