Open ViktorHofer opened 5 months ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
@MichaelSimons @mmitche does anything speak against supporting this? If not, I would be willing to submit a PR.
Nothing is coming to mind as to why we shouldn't support this. It would help clean up several Directory.Packages.props files (example)and improve the UB/SB dev UX.
Example: https://github.com/dotnet/templating/blob/5e4bdc5bb02e0fe73e4b962b85bc0f2dd97607de/Directory.Packages.props#L45-L57
That code block exists because the source-build / VMR infrastructure only overrides properties but not PackageVersion items for the corresponding package identities. This isn't a problem for versions that are updated by Maestro as it doesn't support CPM yet but for any package version that is directly listed in Directory.Packages.props it would be great if the infra could support such.