-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Update dotnet-ef to roll forward across major .NET Core versions #19515
Conversation
Hmm, no validation build got kicked off. I suspect the org change busted our AzDO integration. This is important here because I wanted to double-check the created package @mmitche @Pilchie @wtgodbe @JunTaoLuo @anurse what needs to happen to get our pipelines running again? Is it just renaming the pipelines too? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Thanks @mmitche❕ |
Things got very confused as pipelines were renamed. Closing and reopening… |
@BrennanConroy and @Pilchie just updated the pipelines so builds should be triggering now. |
Thanks for doing that work @BrennanConroy❕ |
BTW I'll sign off once I see the added tag in action i.e. once the validation builds produce artifacts. |
Shoot. I forgot we don't create package artifacts for PR builds of forks. @bricelam I suggest checking this in and checking the next official build to make sure this works as expected. |
This should unblock dotnet/aspnetcore#17947