-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[main] Update dependencies from dotnet/arcade dotnet/xharness dotnet/roslyn-analyzers #65068
[main] Update dependencies from dotnet/arcade dotnet/xharness dotnet/roslyn-analyzers #65068
Conversation
…208.1 Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.ApiCompat , Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.GenAPI , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.GenFacades , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.Helix.Sdk From Version 2.5.1-beta.22103.1 -> To Version 2.5.1-beta.22108.1
@MaximLipnin FYI |
…uild 20220208.1 Microsoft.CodeAnalysis.NetAnalyzers From Version 7.0.0-preview1.22107.2 -> To Version 7.0.0-preview1.22108.1
@MattGal seems like your thing worked but I am not sure it had the intended effect?
So basically we went from "builds start failing when we remove the queue" to "builds start failing 3 weeks when the EOL warning start (so without any notice)"? |
@MattGal there is no successor for I think we should maybe add one more feature - when setting EOL for a queue, we could recommend successor which would be nice for end users because they will get an actionable warning in their builds. And for us, we can have an alert 6 weeks prior for queues that don't have a successor set. We would then prevent situation like this where we don't have an alternative for an EOL'd queues |
…209.1 Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.ApiCompat , Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.GenAPI , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.GenFacades , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.Helix.Sdk From Version 2.5.1-beta.22103.1 -> To Version 2.5.1-beta.22109.1
…20209.1 Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 1.0.0-prerelease.22108.1 -> To Version 1.0.0-prerelease.22109.1
…uild 20220209.1 Microsoft.CodeAnalysis.NetAnalyzers From Version 7.0.0-preview1.22107.2 -> To Version 7.0.0-preview1.22109.1
I mean, that's an interesting feature creep that requires a lot of human labor. An alternative here would be to simply run the SendToHelix task in an msbuild environment where warnings are not set as errors, which is why this warning was promoted to being an error. We've already tried just logging a message that used logging commands to be a warning in the build, this was ignored. |
But this doesn't solve the problem that we start showing EOL to clients with no alternative to migrate to. I don't think that's a good experience for the client teams? It's not a lot of work too - we are already doing extra work when EOL warning starts for a queue, I think adding one more record to the YAML is not too crazy a requirement? |
…210.7 Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.TargetFramework , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.ApiCompat , Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.GenAPI , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.GenFacades , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.Helix.Sdk From Version 2.5.1-beta.22103.1 -> To Version 2.5.1-beta.22110.7
…20210.1 Microsoft.DotNet.XHarness.CLI , Microsoft.DotNet.XHarness.TestRunners.Common , Microsoft.DotNet.XHarness.TestRunners.Xunit From Version 1.0.0-prerelease.22108.1 -> To Version 1.0.0-prerelease.22110.1
This pull request updates the following dependencies
From https://github.com/dotnet/arcade
From https://github.com/dotnet/roslyn-analyzers
From https://github.com/dotnet/xharness