[automated] Merge branch 'release/8.0.1xx' => 'release/8.0.4xx'

[github-actions]

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

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

• nagilson
• dotnet-bot
• marcpopMSFT
• vseanreesermsft
• dsplaisted
• DonnaChen888
• 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/8.0.1xx
git pull --ff-only
git checkout release/8.0.4xx
git pull --ff-only
git merge --no-ff release/8.0.1xx

# 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/sdk HEAD:merge/release/8.0.1xx-to-release/8.0.4xx

or if you are using SSH

git push git@github.com:dotnet/sdk HEAD:merge/release/8.0.1xx-to-release/8.0.4xx

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/8.0.1xx-to-release/8.0.4xx'. This can be done to resolve conflicts or make other changes to this pull request before it is merged.
The provided examples assume that the remote is named 'origin'. If you have a different remote name, please replace 'origin' with the name of your remote.

git fetch
git checkout -b merge/release/8.0.1xx-to-release/8.0.4xx origin/release/8.0.4xx
git pull https://github.com/dotnet/sdk merge/release/8.0.1xx-to-release/8.0.4xx
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/sdk HEAD:merge/release/8.0.1xx-to-release/8.0.4xx

or if you are using SSH

git fetch
git checkout -b merge/release/8.0.1xx-to-release/8.0.4xx origin/release/8.0.4xx
git pull git@github.com:dotnet/sdk merge/release/8.0.1xx-to-release/8.0.4xx
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/sdk HEAD:merge/release/8.0.1xx-to-release/8.0.4xx

Contact .NET Core Engineering (dotnet/dnceng) if you have questions or issues.
Also, if this PR was generated incorrectly, help us fix it. See https://github.com/dotnet/arcade/blob/main/.github/workflows/scripts/inter-branch-merge.ps1.

[nagilson]

Note

This comment was generated by GitHub Copilot on behalf of @nagilson (build duty).

Resolved the merge conflict. Only src/Cli/dotnet/Installer/Windows/MsiPackageCache.cs conflicted: release/8.0.1xx called the local MoveAndSecureFile(...) while release/8.0.4xx moved it into SecurityUtils.MoveAndSecureFile(...). Both retain the security fix; I kept the newer target-branch (8.0.4xx) form, which is the only compilable option since the local method no longer exists in the merged tree.

[nagilson]

Note

This comment was generated by GitHub Copilot on behalf of @nagilson (build duty).

Correction: my first resolution left a silent bad auto-merge in WindowsUtils.cs — 8.0.1xx defined the security helpers inline while 8.0.4xx moved them into SecurityUtils, and git textually combined both, producing duplicate members (CS0111 x16, caught by the TemplateEngine build leg). I force-pushed a corrected merge that takes the newer branch's (8.0.4xx) WindowsUtils.cs verbatim. Verified: base 8.0.4xx is a superset of 8.0.1xx's methods (nothing lost) and the merged tree is now identical to 8.0.4xx.