[automated] Merge branch 'release/3.0' => 'release/3.1'

[dotnet-maestro-bot]

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

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

• @dotnet-maestro[bot]

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/3.0
git pull --ff-only
git checkout release/3.1
git pull --ff-only
git merge --no-ff release/3.0

# 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/3.0-to-release/3.1

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/AspNetCore HEAD:merge/release/3.0-to-release/3.1

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/3.0-to-release/3.1'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.

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

or if you are using SSH

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

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.

[dotnet-maestro-bot]

This pull request has been updated.

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

• @javiercn
• @dotnet-maestro[bot]

[javiercn]

Approve WRT SPA templates changes.

@dougbu Can I just merge it next time or do you prefer doing it yourself. I'm not sure if I have to pay attention to the Versions and things like that on the PR or if that is supposed to be correct always thanks to the bot.

[dotnet-maestro-bot]

This pull request has been updated.

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

• @dotnet-maestro[bot]
• @javiercn

[dougbu]

@javiercn I encourage everyone to merge these merge bot PRs once any conflicts are resolved and the validations succeed.

The only unusual thing here is so many dependency updates coming through. That's happening only because the versioning bot hasn't brought enough into 'release/3.1' to cause conflicts.

[javiercn]

@javiercn I encourage everyone to merge these merge bot PRs once any conflicts are resolved and the validations succeed.

The only unusual thing here is so many dependency updates coming through. That's happening only because the versioning bot hasn't brought enough into 'release/3.1' to cause conflicts.

Well, I'm actually not allowed to merge :)

[dougbu]

Well, I'm actually not allowed to merge :)

We'll look at the branch protection rules later today.