[manual] Merge release/8.0-staging into release/8.0 - #133957
Merged
Merged
Conversation
…et#131209) Fixes dotnet#130860 main PR N/A — servicing-only. `main` has the `Exists(...)` guards (dotnet#121927) and its iOS device tests are still enabled. # Description dotnet#130473 marked the only two test projects this leg selects as `IgnoreForCI`, since the servicing test infra isn't being updated for newer macOS: - `iOS.Device.Aot.Test` - `iOS.Device.ExportManagedSymbols.Test` That suppresses `ArchiveTests`/`_CopyTestArchive`, so the leg no longer produces `artifacts/helix/tests` — and release/8.0's `sendtohelix-mobile.targets:87` enumerates that directory unguarded: ``` error MSB4184: The expression "[System.IO.Directory]::GetDirectories(.../artifacts/helix/tests/, *.app, ...)" cannot be evaluated. Could not find a part of the path '.../artifacts/helix/tests' ``` This keeps the iOS NativeAOT **build** and skips only its now-empty `Send to Helix` step. tvOS is untouched. Both call sites are updated — `runtime.yml` duplicates the block, so fixing only the extra-platforms template would leave the `runtime` definition red. Backporting just the `Exists(...)` guard doesn't work: it trades MSB4184 for `No helix work items` at `sendtohelixhelp.proj:304`, since the leg still has nothing to submit. # Customer Impact None to customers — CI infrastructure only, no shipping bits change. The leg currently fails on every rolling build and every PR touching libraries or coreclr, which keeps .NET 8 servicing CI red (`blocking-clean-ci`) and buries real regressions in noise. # Regression Yes, from dotnet#130473 — which correctly disabled unrunnable device tests but left the Helix submission leg scheduled with nothing to send. CI-only; no shipped code involved. # Testing `Send to Helix` step results on this PR: | Build | Definition | Job | Result | |---|---|---|---| | 1541064 | runtime-extra-platforms | `ios-arm64 Release AllSubsets_NativeAOT` | skipped | | 1541064 | runtime-extra-platforms | `tvos-arm64 Release AllSubsets_NativeAOT` | succeeded | | 1541066 | runtime | `ios-arm64 Release AllSubsets_NativeAOT` | skipped | | 1541066 | runtime | `tvos-arm64 Release AllSubsets_NativeAOT` | succeeded | All four parent jobs succeeded, so iOS build coverage is retained. The tvOS step log confirms a real submission (1 work item, 3.3M payload, Helix job completing with 2 finished work items) — it isn't silently skipping too. Also verified locally with a harness importing the real `sendtohelix-mobile.targets` at the dotnet#130473 commit, which reproduces the MSB4184 and the guard-only follow-on failure. The equivalent leg on release/10.0 is green, so no change is needed elsewhere. # Risk Low. - Pipeline YAML only — no product, package, or test source touched. - Scoped by `osGroup`, so only the iOS NativeAOT leg changes; verified in CI rather than assumed. - Existing `librariesContainsChange`/`coreclrContainsChange`/`isRollingBuild` gating is preserved, just wrapped in `and(...)`. - Uses the existing `condition` hook in `eng/pipelines/libraries/helix.yml` instead of loosening shared Helix behavior for all mobile lanes. - Worst case: iOS NativeAOT test coverage stays absent — already the status quo, since both tests are disabled. Both call sites carry a comment to remove the exclusion if these tests are re-enabled. > [!NOTE] > This pull request description was generated with GitHub Copilot. Copilot-Session: 332b1207-8473-4b2b-8864-30da72ee4f6b
…ts (dotnet#132119) Backport of dotnet#131955 to release/8.0-staging /cc @mrek-msft @Copilot ## Customer Impact - [ ] Customer reported - [ ] Found internally [Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.] ## Regression - [ ] Yes - [ ] No [If yes, specify when the regression was introduced. Provide the PR or commit if known.] ## Testing [How was the fix verified? How was the issue missed previously? What tests were added?] ## Risk [High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.] **IMPORTANT**: If this backport is for a servicing release, please verify that: - For .NET 8 and .NET 9: The PR target branch is `release/X.0-staging`, not `release/X.0`. - For .NET 10+: The PR target branch is `release/X.0` (no `-staging` suffix). ## Package authoring no longer needed in .NET 9 **IMPORTANT**: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version. Keep in mind that we still need package authoring in .NET 8 and older versions. Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: eiriktsarpalis <2813363+eiriktsarpalis@users.noreply.github.com>
…et#132255) 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: * hoyosjs * vseanreesermsft * dotnet-bot * iremyux ## 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. <img alt="merge button instructions" src="https://i.imgur.com/GepcNJV.png" width="300" /> 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. ``` sh 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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` <details> <summary>or if you are using SSH</summary> ``` git push git@github.com:dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` </details> After PR checks are complete push the branch ``` 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][resolve-github] or using the [command line][resolve-cli]. [resolve-github]: https://help.github.com/articles/resolving-a-merge-conflict-on-github/ [resolve-cli]: https://help.github.com/articles/resolving-a-merge-conflict-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. 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-to-release/8.0-staging origin/release/8.0-staging git pull https://github.com/dotnet/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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` <details> <summary>or if you are using SSH</summary> ``` git fetch git checkout -b merge/release/8.0-to-release/8.0-staging origin/release/8.0-staging git pull git@github.com:dotnet/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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` </details> 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.
…ng oversized Content-Length cases to managed implementation (dotnet#132651) Backport of dotnet#132321 to release/8.0-staging /cc @akoeplinger @alinpahontu2912 ## Customer Impact - [ ] Customer reported - [ ] Found internally [Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.] ## Regression - [ ] Yes - [ ] No [If yes, specify when the regression was introduced. Provide the PR or commit if known.] ## Testing [How was the fix verified? How was the issue missed previously? What tests were added?] ## Risk [High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.] **IMPORTANT**: If this backport is for a servicing release, please verify that: - For .NET 8 and .NET 9: The PR target branch is `release/X.0-staging`, not `release/X.0`. - For .NET 10+: The PR target branch is `release/X.0` (no `-staging` suffix). ## Package authoring no longer needed in .NET 9 **IMPORTANT**: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version. Keep in mind that we still need package authoring in .NET 8 and older versions. Co-authored-by: Stefan-Alin Pahontu <56953855+alinpahontu2912@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Irem Yuksel <113098562+iremyux@users.noreply.github.com> Copilot-Session: bcc5e304-cc27-44b0-aac3-b9eada42d13f
…t#132383) This pull request updates the following dependencies [marker]: <> (Begin:3c89df73-24a9-48a4-8224-08dbcfd3ad70) ## From https://github.com/dotnet/xharness - **Subscription**: [3c89df73-24a9-48a4-8224-08dbcfd3ad70](https://maestro.dot.net/subscriptions?search=3c89df73-24a9-48a4-8224-08dbcfd3ad70) - **Build**: [20260819.1](https://dev.azure.com/dnceng/internal/_build/results?buildId=3051693) ([327705](https://maestro.dot.net/channel/2/github:dotnet:xharness/build/327705)) - **Date Produced**: August 19, 2026 8:47:15 AM UTC - **Commit**: [8dd9b8e6004e22c7b120af0631f0809865ff2088](dotnet/xharness@8dd9b8e) - **Branch**: [main](https://github.com/dotnet/xharness/tree/main) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [11.0.0-prerelease.26370.1 to 11.0.0-prerelease.26419.1][2] - Microsoft.DotNet.XHarness.CLI - Microsoft.DotNet.XHarness.TestRunners.Common - Microsoft.DotNet.XHarness.TestRunners.Xunit [2]: dotnet/xharness@65e5795...8dd9b8e [DependencyUpdate]: <> (End) [marker]: <> (End:3c89df73-24a9-48a4-8224-08dbcfd3ad70) --------- Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: vitek-karas <10670590+vitek-karas@users.noreply.github.com>
…t#132959) This pull request updates the following dependencies [marker]: <> (Begin:3c89df73-24a9-48a4-8224-08dbcfd3ad70) ## From https://github.com/dotnet/xharness - **Subscription**: [3c89df73-24a9-48a4-8224-08dbcfd3ad70](https://maestro.dot.net/subscriptions?search=3c89df73-24a9-48a4-8224-08dbcfd3ad70) - **Build**: [20260828.1](https://dev.azure.com/dnceng/internal/_build/results?buildId=3060005) ([329158](https://maestro.dot.net/channel/2/github:dotnet:xharness/build/329158)) - **Date Produced**: August 28, 2026 2:17:22 PM UTC - **Commit**: [b355c0507b19670c2d386677d7f99260f07cefa5](dotnet/xharness@b355c05) - **Branch**: [main](https://github.com/dotnet/xharness/tree/main) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [11.0.0-prerelease.26419.1 to 11.0.0-prerelease.26428.1][1] - Microsoft.DotNet.XHarness.CLI - Microsoft.DotNet.XHarness.TestRunners.Common - Microsoft.DotNet.XHarness.TestRunners.Xunit [1]: dotnet/xharness@8dd9b8e...b355c05 [DependencyUpdate]: <> (End) [marker]: <> (End:3c89df73-24a9-48a4-8224-08dbcfd3ad70) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Backport of dotnet#133097 to `release/8.0-staging`. Fixes dotnet#133096. ## Customer Impact - [ ] Customer reported - [X] Found internally Customers would be unable to establish QUIC or HTTP/3 connections on Linux without providing the target host name (to verify against the server certificate). ## Regression - [X] Yes - [ ] No Regression by updating MsQuic (optional dependency to light-up QUIC support) ## Testing Affected tests succeed on CI. ## Risk Low, change is small and well understood. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…132995) This pull request updates the following dependencies [marker]: <> (Begin:f3ed209d-980c-4076-a437-08dbcfd61a5a) ## From https://github.com/dotnet/arcade - **Subscription**: [f3ed209d-980c-4076-a437-08dbcfd61a5a](https://maestro.dot.net/subscriptions?search=f3ed209d-980c-4076-a437-08dbcfd61a5a) - **Build**: [20260831.7](https://dev.azure.com/dnceng/internal/_build/results?buildId=3062498) ([329605](https://maestro.dot.net/channel/3885/github:dotnet:arcade/build/329605)) - **Date Produced**: September 1, 2026 12:46:11 AM UTC - **Commit**: [25da4e8f08fab05a39c27443df99b96d738f3c82](dotnet/arcade@25da4e8) - **Branch**: [release/8.0](https://github.com/dotnet/arcade/tree/release/8.0) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [8.0.0-beta.26371.5 to 8.0.0-beta.26431.7][1] - Microsoft.DotNet.Arcade.Sdk - Microsoft.DotNet.Build.Tasks.Archives - Microsoft.DotNet.Build.Tasks.Feed - Microsoft.DotNet.Build.Tasks.Installers - Microsoft.DotNet.Build.Tasks.Packaging - Microsoft.DotNet.Build.Tasks.TargetFramework - Microsoft.DotNet.Build.Tasks.Templating - Microsoft.DotNet.Build.Tasks.Workloads - Microsoft.DotNet.CodeAnalysis - Microsoft.DotNet.GenAPI - Microsoft.DotNet.GenFacades - Microsoft.DotNet.Helix.Sdk - Microsoft.DotNet.PackageTesting - Microsoft.DotNet.RemoteExecutor - Microsoft.DotNet.SharedFramework.Sdk - Microsoft.DotNet.VersionTools.Tasks - Microsoft.DotNet.XUnitExtensions - From [2.5.1-beta.26371.5 to 2.5.1-beta.26431.7][1] - Microsoft.DotNet.XUnitConsoleRunner [1]: dotnet/arcade@444c2ef...25da4e8 [DependencyUpdate]: <> (End) [marker]: <> (End:f3ed209d-980c-4076-a437-08dbcfd61a5a) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…ENTIALS in QUIC (dotnet#133090) ## Customer Impact - [ ] Customer reported - [x] Found internally A recent update in MsQuic changed an error code returned when applicaiton attempted to use certificates with ephemeral keys (Windows-only concept where keys are not persisted in a key store, Schannel, the TLS provider on Windows does not work with such certificates). This causes to a hard-to-diagnose exception being surfaced to .NET application. This change: - fixes the error detection so that more helpful diagnostic exception is surfaced - fixes test failures to de-noise CI. ## Regression - [X] Yes - [ ] No Regression was introduced by updating MsQuic to the latest version. ## Testing verified in CI. ## Risk Low, the fix is contained and well understood. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: rzikm <32671551+rzikm@users.noreply.github.com>
…et#133114) 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: * vseanreesermsft ## 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. <img alt="merge button instructions" src="https://i.imgur.com/GepcNJV.png" width="300" /> 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. ``` sh 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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` <details> <summary>or if you are using SSH</summary> ``` git push git@github.com:dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` </details> After PR checks are complete push the branch ``` 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][resolve-github] or using the [command line][resolve-cli]. [resolve-github]: https://help.github.com/articles/resolving-a-merge-conflict-on-github/ [resolve-cli]: https://help.github.com/articles/resolving-a-merge-conflict-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. 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-to-release/8.0-staging origin/release/8.0-staging git pull https://github.com/dotnet/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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` <details> <summary>or if you are using SSH</summary> ``` git fetch git checkout -b merge/release/8.0-to-release/8.0-staging origin/release/8.0-staging git pull git@github.com:dotnet/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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` </details> 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.
…otnet#133386) This pull request updates the following dependencies [marker]: <> (Begin:855db5a2-4d17-4346-a439-08dbcfd61a5a) ## From https://github.com/dotnet/runtime-assets - **Subscription**: [855db5a2-4d17-4346-a439-08dbcfd61a5a](https://maestro.dot.net/subscriptions?search=855db5a2-4d17-4346-a439-08dbcfd61a5a) - **Build**: [20260907.3](https://dev.azure.com/dnceng/internal/_build/results?buildId=3068607) ([330758](https://maestro.dot.net/channel/3073/github:dotnet:runtime-assets/build/330758)) - **Date Produced**: September 7, 2026 11:00:01 AM UTC - **Commit**: [28197b1af8bfa73dc553aab7b62f8a2e8945b79c](dotnet/runtime-assets@28197b1) - **Branch**: [release/8.0](https://github.com/dotnet/runtime-assets/tree/release/8.0) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [8.0.0-beta.26404.3 to 8.0.0-beta.26457.3][1] - Microsoft.DotNet.CilStrip.Sources - System.ComponentModel.TypeConverter.TestData - System.Data.Common.TestData - System.Drawing.Common.TestData - System.Formats.Tar.TestData - System.IO.Compression.TestData - System.IO.Packaging.TestData - System.Net.TestData - System.Private.Runtime.UnicodeData - System.Runtime.Numerics.TestData - System.Runtime.TimeZoneData - System.Security.Cryptography.X509Certificates.TestData - System.Text.RegularExpressions.TestData - System.Windows.Extensions.TestData [1]: dotnet/runtime-assets@79d10a3...28197b1 [DependencyUpdate]: <> (End) [marker]: <> (End:855db5a2-4d17-4346-a439-08dbcfd61a5a) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
) This pull request updates the following dependencies [marker]: <> (Begin:e82a8e07-8d2b-4a71-e90f-08dbcfd41ade) ## From https://github.com/dotnet/icu - **Subscription**: [e82a8e07-8d2b-4a71-e90f-08dbcfd41ade](https://maestro.dot.net/subscriptions?search=e82a8e07-8d2b-4a71-e90f-08dbcfd41ade) - **Build**: [20260907.3](https://dev.azure.com/dnceng/internal/_build/results?buildId=3068612) ([330775](https://maestro.dot.net/channel/3073/github:dotnet:icu/build/330775)) - **Date Produced**: September 7, 2026 11:29:50 AM UTC - **Commit**: [a9feff780c8749eb6e39c356abe4eef38c0ce40e](dotnet/icu@a9feff7) - **Branch**: [dotnet/release/8.0](https://github.com/dotnet/icu/tree/dotnet/release/8.0) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [8.0.0-rtm.26407.4 to 8.0.0-rtm.26457.3][1] - Microsoft.NETCore.Runtime.ICU.Transport [1]: dotnet/icu@1ed1640...a9feff7 [DependencyUpdate]: <> (End) [marker]: <> (End:e82a8e07-8d2b-4a71-e90f-08dbcfd41ade) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…t#133334) This pull request updates the following dependencies [marker]: <> (Begin:3c89df73-24a9-48a4-8224-08dbcfd3ad70) ## From https://github.com/dotnet/xharness - **Subscription**: [3c89df73-24a9-48a4-8224-08dbcfd3ad70](https://maestro.dot.net/subscriptions?search=3c89df73-24a9-48a4-8224-08dbcfd3ad70) - **Build**: [20260901.1](https://dev.azure.com/dnceng/internal/_build/results?buildId=3063443) ([329852](https://maestro.dot.net/channel/2/github:dotnet:xharness/build/329852)) - **Date Produced**: September 1, 2026 9:01:52 PM UTC - **Commit**: [1fc9369e393e63fa8760afb30d2fcc596bb799bf](dotnet/xharness@1fc9369) - **Branch**: [main](https://github.com/dotnet/xharness/tree/main) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [11.0.0-prerelease.26428.1 to 11.0.0-prerelease.26451.1][1] - Microsoft.DotNet.XHarness.CLI - Microsoft.DotNet.XHarness.TestRunners.Common - Microsoft.DotNet.XHarness.TestRunners.Xunit [1]: dotnet/xharness@b355c05...1fc9369 [DependencyUpdate]: <> (End) [marker]: <> (End:3c89df73-24a9-48a4-8224-08dbcfd3ad70) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…t#133845) This pull request updates the following dependencies [marker]: <> (Begin:3c89df73-24a9-48a4-8224-08dbcfd3ad70) ## From https://github.com/dotnet/xharness - **Subscription**: [3c89df73-24a9-48a4-8224-08dbcfd3ad70](https://maestro.dot.net/subscriptions?search=3c89df73-24a9-48a4-8224-08dbcfd3ad70) - **Build**: [20260911.1](https://dev.azure.com/dnceng/internal/_build/results?buildId=3072980) ([331573](https://maestro.dot.net/channel/2/github:dotnet:xharness/build/331573)) - **Date Produced**: September 11, 2026 11:35:21 AM UTC - **Commit**: [cf433ea2eff13305b60c8871a03115b1dbb600f8](dotnet/xharness@cf433ea) - **Branch**: [main](https://github.com/dotnet/xharness/tree/main) [DependencyUpdate]: <> (Begin) - **Dependency Updates**: - From [11.0.0-prerelease.26451.1 to 11.0.0-prerelease.26461.1][1] - Microsoft.DotNet.XHarness.CLI - Microsoft.DotNet.XHarness.TestRunners.Common - Microsoft.DotNet.XHarness.TestRunners.Xunit [1]: dotnet/xharness@1fc9369...cf433ea [DependencyUpdate]: <> (End) [marker]: <> (End:3c89df73-24a9-48a4-8224-08dbcfd3ad70) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
…et#133623) 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: * ViveliDuCh * 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. <img alt="merge button instructions" src="https://i.imgur.com/GepcNJV.png" width="300" /> 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. ``` sh 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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` <details> <summary>or if you are using SSH</summary> ``` git push git@github.com:dotnet/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` </details> After PR checks are complete push the branch ``` 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][resolve-github] or using the [command line][resolve-cli]. [resolve-github]: https://help.github.com/articles/resolving-a-merge-conflict-on-github/ [resolve-cli]: https://help.github.com/articles/resolving-a-merge-conflict-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. 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-to-release/8.0-staging origin/release/8.0-staging git pull https://github.com/dotnet/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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` <details> <summary>or if you are using SSH</summary> ``` git fetch git checkout -b merge/release/8.0-to-release/8.0-staging origin/release/8.0-staging git pull git@github.com:dotnet/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/runtime HEAD:merge/release/8.0-to-release/8.0-staging ``` </details> 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.
|
Azure Pipelines: Successfully started running 4 pipeline(s). 12 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @karelz, @dotnet/ncl |
Contributor
There was a problem hiding this comment.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Note
This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.
This was referenced Sep 15, 2026
mrek-msft
approved these changes
Sep 15, 2026
This was referenced Sep 15, 2026
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.