Pinning package version for packages not being serviced#46224
Pinning package version for packages not being serviced#46224Anipik merged 1 commit intodotnet:release/5.0from Anipik:pin
Conversation
|
Tagging subscribers to this area: @safern, @ViktorHofer Issue DetailsThis change fixes the problem of inconsistent package index. when we build with the stable flag on , the build system updates the package index to reflect the new package version as stable which is not true. This is also required for sourcebuild which builds all the packages in servicing release as well
|
|
@safern @ViktorHofer @ericstj can u review this one ? |
|
Thank you for doing this @Anipik. I wasn't sure if this change would be sufficient: we should double check the packages produced in 5.0.3 and make sure we aren't clashing with an GA identities. If we are, we might need to opt those packages into the incremented version. |
what do u mean by GA identities ? are you referring to GA package version ? |
|
Yeah, just to make sure we don't try to republish any of the exact same package versions that we built in the GA build. I'm not too concerned with Libraries, moreso the other random packages that build in coreclr and installer. Do any of those rely on being auto-incremented? |
i will do a complete build and verify that |
This change fixes the problem of inconsistent package index. when we build with the stable flag on , the build system updates the package index to reflect the new package version as stable which is not true for packages not being serviced.
This is also required for sourcebuild which builds all the packages in servicing release as well