[automated] Merge branch 'release/8.0' => 'release/8.0-staging' by dotnet-maestro-bot · Pull Request #101098 · dotnet/runtime

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-maestro-bot · 2024-04-16T03:45:45Z

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

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

directhex
vseanreesermsft
dotnet-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
git pull --ff-only
git checkout release/8.0-staging
git pull --ff-only
git merge --no-ff release/8.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/runtime HEAD:merge/release/8.0-to-release/8.0-staging

or if you are using SSH

git push git@github.com:dotnet-maestro-bot/runtime HEAD:merge/release/8.0-to-release/8.0-staging

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

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

or if you are using SSH

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

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.

…-merge-8.0-2024-04-09-1217

…8.0-2024-04-09-1217 Merging internal commits for release/8.0

[manual] Merge release/8.0-staging into release/8.0

dotnet-policy-service · 2024-04-16T03:46:18Z

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

…otnet#101145) * Update MicrosoftBuildVersion to latest to fix System.Security.Cryptography.XML component governance alert. * Add info to VersionDetails to allow sourcebuild to update the MSBuild dependency * Update SourceBuildPrebuiltBaseline.xml --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Parker Bibus <parkerbibus@microsoft.com> Co-authored-by: Eric StJohn <ericstj@microsoft.com> Co-authored-by: Michael Simons <msimons@microsoft.com>

dotnet-botand others added 11 commits March 6, 2024 19:20

Merge in 'release/8.0' changes
520bd2e

Merge in 'release/8.0' changes
367136d

Merge in 'release/8.0' changes
5cff8b8

Merge in 'release/8.0' changes
38f2042

Merge in 'release/8.0' changes
a1a9440

Merge in 'release/8.0' changes
2d7eea2

Update branding to 8.0.5 (dotnet#100547)
f8132e6

Merge commit '2d7eea252964e69be94cb9c847b371b23e4dd470' into internal…
35f3191
…-merge-8.0-2024-04-09-1217

Merge pull requestdotnet#100835from vseanreesermsft/internal-merge-…
8966d08
…8.0-2024-04-09-1217 Merging internal commits for release/8.0

Merge branch 'release/8.0' into release/8.0-staging
befe7ad

Merge pull requestdotnet#101091from directhex/release/8.0-staging
b55fd6f
[manual] Merge release/8.0-staging into release/8.0

ghost added the area-Infrastructure-libraries label Apr 16, 2024

carlossanlop approved these changes Apr 29, 2024
View reviewed changes

carlossanlop added the Servicing-approved Approved for servicing release label Apr 29, 2024

carlossanlop mentioned this pull request Apr 29, 2024
[8.0] Test failure in System.Diagnostics.Tests.ProcessTests.MainWindowHandle_GetWithGui_ShouldRefresh_Windows #101700
Closed

carlossanlop merged commit 6fa6fb7 into dotnet:release/8.0-stagingApr 29, 2024

github-actionsBot locked and limited conversation to collaborators May 31, 2024