Skip to content

[automated] Merge branch 'release/10.0.2xx' => 'release/10.0.3xx'#53679

Merged
DonnaChen888 merged 13 commits intorelease/10.0.3xxfrom
merge/release/10.0.2xx-to-release/10.0.3xx
Apr 14, 2026
Merged

[automated] Merge branch 'release/10.0.2xx' => 'release/10.0.3xx'#53679
DonnaChen888 merged 13 commits intorelease/10.0.3xxfrom
merge/release/10.0.2xx-to-release/10.0.3xx

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Apr 2, 2026

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

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

  • joeloff
  • 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.

merge button instructions

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/10.0.2xx
git pull --ff-only
git checkout release/10.0.3xx
git pull --ff-only
git merge --no-ff release/10.0.2xx

# 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/10.0.2xx-to-release/10.0.3xx
or if you are using SSH
git push git@github.com:dotnet/sdk HEAD:merge/release/10.0.2xx-to-release/10.0.3xx

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/10.0.2xx-to-release/10.0.3xx'. 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/10.0.2xx-to-release/10.0.3xx origin/release/10.0.3xx
git pull https://github.com/dotnet/sdk merge/release/10.0.2xx-to-release/10.0.3xx
(make changes)
git commit -m "Updated PR with my changes"
git push https://github.com/dotnet/sdk HEAD:merge/release/10.0.2xx-to-release/10.0.3xx
or if you are using SSH
git fetch
git checkout -b merge/release/10.0.2xx-to-release/10.0.3xx origin/release/10.0.3xx
git pull git@github.com:dotnet/sdk merge/release/10.0.2xx-to-release/10.0.3xx
(make changes)
git commit -m "Updated PR with my changes"
git push git@github.com:dotnet/sdk HEAD:merge/release/10.0.2xx-to-release/10.0.3xx

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.

dotnet-maestro Bot and others added 8 commits April 2, 2026 02:05
…260401.3

On relative base path root
Microsoft.Testing.Platform From Version 2.2.1-preview.26180.5 -> To Version 2.2.1-preview.26201.3
MSTest From Version 4.2.1-preview.26180.5 -> To Version 4.2.1-preview.26201.3
…260401.3

On relative base path root
Microsoft.Testing.Platform From Version 2.2.1-preview.26180.5 -> To Version 2.2.1-preview.26201.3
MSTest From Version 4.2.1-preview.26180.5 -> To Version 4.2.1-preview.26201.3
Reset patterns:
- global.json
- NuGet.config
- eng/Version.Details.xml
- eng/Version.Details.props
- eng/common/*
Reset patterns:
- global.json
- NuGet.config
- eng/Version.Details.xml
- eng/Version.Details.props
- eng/common/*
@DonnaChen888
Copy link
Copy Markdown
Contributor

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@marcpopMSFT
Copy link
Copy Markdown
Member

The only change in this PR is breaking the tests. I think the version of MTP in 3xx is behind 2xx. @dotnet/dotnet-testing how soon is the update coming? Seems like dotnet/dotnet#5511 is blocked.

I can close this, remove the extra baseline code (which will make this PR empty and make the flow back from 3xx fail once that other PR is in), or leave this open.

@Youssef1313
Copy link
Copy Markdown
Member

@marcpopMSFT The test updates in this PR were originally paired with a dependency update of MTP. Why is this PR only getting the test update without the dependency update?

@Youssef1313
Copy link
Copy Markdown
Member

Youssef1313 commented Apr 7, 2026

Original PR from 10.0.2xx is #53669

@Youssef1313
Copy link
Copy Markdown
Member

Looks like wrong merge or conflict resolution that happened in this PR. I pushed some changes.

@marcpopMSFT
Copy link
Copy Markdown
Member

Looks like wrong merge or conflict resolution that happened in this PR. I pushed some changes.

Guidance to our team is to take the target branch for any eng folder merge conflicts. Occasionally, if there are eng folder changes with no conflicts, those slip through so this might have been a case like that.

dsplaisted and others added 2 commits April 9, 2026 12:08
The automated merge from release/10.0.2xx overwrote the 10.0.3xx
version of the snapshot file. The two branches have legitimately
different help output (10.0.2xx has --show-stderr/--show-stdout,
10.0.3xx has --artifacts-path instead). Restore the 10.0.3xx version.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The automated merge from release/10.0.2xx incorrectly overwrote
dependency versions in Version.Details.props and Version.Details.xml.
These files contain dependency versions managed by Maestro/darc and
should not be updated by inter-branch merges — each branch has its
own dependency flow. The merge downgraded ~60 package versions from
26203 builds to older 26201 builds and changed NuGet, Roslyn, and
testing platform versions to incompatible values.

Restore both files to match release/10.0.3xx.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@DonnaChen888
Copy link
Copy Markdown
Contributor

Known issue dotnet/dnceng#6496

@DonnaChen888
Copy link
Copy Markdown
Contributor

/ba-g no file changes

@DonnaChen888 DonnaChen888 merged commit e560ea3 into release/10.0.3xx Apr 14, 2026
8 of 9 checks passed
@DonnaChen888 DonnaChen888 deleted the merge/release/10.0.2xx-to-release/10.0.3xx branch April 14, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants