-
Notifications
You must be signed in to change notification settings - Fork 447
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use asset manifests exclusively to produce/consume previously source built artifacts #19585
Conversation
…bootstrap tarball for the build to find
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't merge this until #19594 is merged and we have a new official build so that we can do a re-bootstrap.
I'm fine holding off on merging. Any other feedback on this PR? |
Look good but please let's wait with merging until Monday. We still haven't got a new SDK out that we can use. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As part of the installer->sdk repository consolidation we are already switching the VMR over into dotnet/sdk. ETA: today or tomorrow. The last manual code sync happened today and we don't plan on doing another sync. Please close this PR and submit it into dotnet/sdk. Sorry for the inconvenience.
Moved to dotnet/sdk as dotnet/sdk#40745 |
Update the consumption of the previously source-built artifacts and the production of the PackageVersions.props to insert into the bootstrap tarball to both be produced from asset manifests.
This allows us to remove the split in the logic between either using the asset manifests or cracking open NuGet packages.