Skip to content

Should conflict resolution lift the versions read from PackageOverrides.txt #49232

Open
@ericstj

Description

@ericstj

#46898 introduced version lifting of packages when producing pruning info.

This was based on the conclusion of #44566 where decided that we wanted the SDK to drop things that were from any version of the same runtime Major.Minor band.

This works when pruning is enabled. Do we want to do the same thing where pruning is not enabled and the packages hit conflict resolution?

@ViktorHofer raised this here: #49092 (comment)

It's somewhat niche, since it would only be newer SDKs and all those SDKs enabled pruning by default for all the frameworks that provide packageoverides.txt, so it would only be for the cases where folks have disabled pruning and want conflict resolution to do the same lifting.

Probably whatever we decide we'd need to think if that would impact the build of dotnet/runtime or workflows (like testing the runtime, testing privates, dev builds, etc).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions