[release/8.0] Update Components dependencies to latest stable versions #3988
Conversation
This file contains 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
dotnet-issue-labeler
bot
added
the
area-integrations
dotnet-policy-service
bot
added
the
Servicing-consider
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
danmoseley
approved these changes
Apr 27, 2024
danmoseley
added
Servicing-approved
davidfowl
approved these changes
Apr 27, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Customer Impact
When customers depend on our components, they should get the latest versions of the underlying libraries that the components bring in.
Testing
Automated tests passing in the repo.
Risk
Low. Our components tests would catch if these new versions cause problems with our code. Most of these updates are already in
main.Regression?
No
Microsoft Reviewers: Open in CodeFlow