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

[dotnet-maestro-bot]

I detected changes in the release/2.1 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 release/2.1 by the following committers:

• @mmitche

Instructions for merging from UI

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

If this repo does not allow creating merge commits from the GitHub UI, use command line instructions.

Instructions for merging via command line

Run these commands to merge this pull request from the command line.

git fetch
git checkout release/2.1
git pull --ff-only
git checkout release/2.2
git pull --ff-only
git merge --no-ff release/2.1

# If there are merge conflicts, resolve them and then run git merge --continue to complete the merge
# Pushing the changes to the PR branch will re-trigger PR validation.
git push https://github.com/dotnet-maestro-bot/AspNetCore HEAD:merge/release/2.1-to-release/2.2

or if you are using SSH

git push [email protected]:dotnet-maestro-bot/AspNetCore HEAD:merge/release/2.1-to-release/2.2

After PR checks are complete push the branch

git push

Instructions for resolving conflicts

⚠️ 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.

Instructions for updating this pull request

Contributors to this repo have permission update this pull request by pushing to the branch 'merge/release/2.1-to-release/2.2'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

git checkout -b merge/release/2.1-to-release/2.2 release/2.2
git pull https://github.com/dotnet-maestro-bot/AspNetCore merge/release/2.1-to-release/2.2
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet-maestro-bot/AspNetCore HEAD:merge/release/2.1-to-release/2.2

or if you are using SSH

git checkout -b merge/release/2.1-to-release/2.2 release/2.2
git pull [email protected]:dotnet-maestro-bot/AspNetCore merge/release/2.1-to-release/2.2
(make changes)
git commit -m "Updated PR with my changes"
git push [email protected]:dotnet-maestro-bot/AspNetCore HEAD:merge/release/2.1-to-release/2.2

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.

[pranavkm]

@dougbu can we merge this in?

[dougbu]

@mmitche should your unpinning of SystemSecurityCryptographyCngPackageVersion be present in the 'release/2.2' branch of this repo?

[dougbu]

@pranavkm once I hear from @mmitche I'll either merge or apply his change manually i.e. make this a non-no-op merge.

[mmitche]

@mmitche should your unpinning of SystemSecurityCryptographyCngPackageVersion be present in the 'release/2.2' branch of this repo?

It did not get produced by corefx, so...i'm not sure...I'll have to follow up and find out whether it needs to be in 2.2

[dougbu]

@pranavkm could you please allow 049cdec to come through? Probably simplest to cherry-pick that commit into this branch or perhaps to redo the merge locally.

[pranavkm]

pranavkm could you please allow 049cdec to come through? Probably simplest to cherry-pick that commit into this branch or perhaps to redo the merge locally.

See 82c73f9

[dougbu]

Suspect this should be closed. But, please confirm there's either a merge PR open pulling 'release/2.1' changes into 'master' or that's already happened.

[JunTaoLuo]

Closing in favour of #17672.