-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Not flowing dependency updates for Microsoft.NETCore.App #14501
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
Comments
Not intentional, but also ...meh. lol, we’ll discuss. I’m certainly not against doing it. |
And also turn by on warnings as errors. |
I'm reverting this in #14643 (comment). It made things way too complicated. |
Re-opening. This is now blocking dependency flow for aspnetcore. See #15680 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This repo is only flowing dependency updates for packages, but not for the actually .NET Core runtime (Microsoft.NETCore.App). That means bot-generated PRs such as #14500 are not actually testing EFCore with the latest .NET Core.
The repo is currently using the runtime version that is baked into the .NET Core SDK. The SDK version is not automatically updated by Arcade, and even if it were, it would often be at least 1 step behind the latest runtime version which will be inserted into the SDK.
@bricelam @ajcvickers - was this an intentional change when converting this repo to Arcade?
The text was updated successfully, but these errors were encountered: