Skip to content

Adding dotnet3.1/dotnet-eng packages sources #13144

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

Merged

Conversation

ChadNedzlek
Copy link
Contributor

In order to remove dependencies on sleet from release branches,
it is neccessary to preemptively add these sources so that mehanisms
will be able to restore these packages.

Sleet must be removed because of it's strong dependency on spcific
nuget.packaging versions, which are not stable between 3.0 and 3.1
causing method load exceptions.

In order to remove dependencies on sleet from release branches,
it is neccessary to preemptively add these sources so that mehanisms
will be able to restore these packages.

Sleet must be removed because of it's strong dependency on spcific
nuget.packaging versions, which are not stable between 3.0 and 3.1
causing method load exceptions.
@ChadNedzlek ChadNedzlek requested a review from mmitche August 26, 2020 23:42
Copy link
Member

@mmitche mmitche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wtgodbe @silvioguiso This is here because we will need to stop publishing packages to dotnet-core for 3.1 because of incompatibilities between the 3.1 SDK and the version of nuget that the dotnet-core feed requires (it's a blob feed).

We are preparing the other side of this change in arcade 3.x. Feel free to check this in when you want, but if builds are working at the moment and not blocked it could wait till the next release.

@wtgodbe wtgodbe merged commit afdde81 into dotnet:release/3.1.1xx Sep 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants