[nightly] Update dependencies from dotnet/dotnet-monitor/9.0#6597
Merged
Conversation
Member
|
It actually did trigger automatically - however, it got overwritten due to Update-dependencies tool can overwrite the wrong pull request. I intended to regenerate/resubmit any Monitor PRs that I had to close due to that bug but you beat me to it. Thanks for being proactive. |
lbussell
approved these changes
Aug 4, 2025
lbussell
pushed a commit
to lbussell/dotnet-docker
that referenced
this pull request
Aug 5, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NOTE - this did not trigger automatically, and was generated manually via the
Set-DotnetVersions.ps1script. I don't have prior experience with this script, but I compared the output with a prior update here. If we should be doing something different, let me or @wiktork know and this can be scrapped/updated.