[automated] Merge branch 'maestro/release/2.2' => 'release/2.2'

[dotnet-maestro-bot]

I detected changes in the maestro/release/2.2 branch which have not been merged yet to release/2.2. I'm a robot and am configured to help you automatically keep release/2.2 up to date, so I've opened this PR.

This PR merges commits made on maestro/release/2.2 by the following committers:

• @aspnetci

Instructions for merging

This PR will not be auto-merged. When pull request checks pass, please complete this PR by creating a merge commit, not a squash or rebase commit.

You can also do this on command line:

git checkout release/2.2
git pull
git fetch --force https://github.com/dotnet-maestro-bot/HttpAbstractions merge/maestro/release/2.2-to-release/2.2:merge/maestro/release/2.2-to-release/2.2
git merge merge/maestro/release/2.2-to-release/2.2
git push

Instructions for resolving conflicts

:warning: If there are merge conflicts, you will need to resolve them manually before merging. You can do this using GitHub or using the command line.

Maintainers of this repo have permission to the branch 'merge/maestro/release/2.2-to-release/2.2' on https://github.com/dotnet-maestro-bot/HttpAbstractions. You can push changes to this branch to resolve conflicts or other issues in this pull request. The bot will attempt to update this branch as more changes are discovered on maestro/release/2.2.

Please contact .NET Core Engineering if you have questions or issues. Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/master/scripts/GitHubMergeBranches.ps1.

[Eilon]

Closing unnecessary dependency update. See https://github.com/aspnet/Infrastructure/issues/84 for details.