Repository navigation
[main] Source code updates from dotnet/dotnet - #15355
Conversation
|
Caution 🚨 Action Required — Conflict detectedA conflict was detected when trying to update this PR with changes from build The conflicts in the following files need to be manually resolved:
ℹ️ To resolve the conflicts, please follow these steps:
💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance. |
|
Hello @dotnet-maestro[bot], I noticed that you’re changing an .swr file or any file under src/Package/MSBuild.VSSetup.. Please make sure to validate this change by an experimental VS insertion. This is accomplished by pushing to an exp/* branch, which requires write permissions to this repo. |
0e51c0b to
c2d014b
Compare
|
Caution 🚨 Action Required — Conflict detectedA conflict was detected when trying to update this PR with changes from build The conflicts in the following files need to be manually resolved:
ℹ️ To resolve the conflicts, please follow these steps:
💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance. |
c2d014b to
571d732
Compare
|
Caution 🚨 Action Required — Conflict detectedA conflict was detected when trying to update this PR with changes from build The conflicts in the following files need to be manually resolved:
ℹ️ To resolve the conflicts, please follow these steps:
💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance. |
571d732 to
cc8a733
Compare
|
Caution 🚨 Action Required — Conflict detectedA conflict was detected when trying to update this PR with changes from build The conflicts in the following files need to be manually resolved:
ℹ️ To resolve the conflicts, please follow these steps:
💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance. |
cc8a733 to
f5e37cd
Compare
|
Caution 🚨 Action Required — Conflict detectedA conflict was detected when trying to update this PR with changes from build The conflicts in the following files need to be manually resolved:
ℹ️ To resolve the conflicts, please follow these steps:
💡 You may consult the FAQ for more information or tag @dotnet/prodconsvcs for assistance. |
Resolve the unsafe release/11.0.2xx backflow without reverting main's 18.14 branding, change wave, OptProf settings, or temp-file guidance. Retain the TaskAnalyzer source-build fixes from dotnet/dotnet#9184 as adapted for release/11.0.2xx in dotnet/dotnet#9867, including Roslyn dependency tracking, source-built overrides, solution inclusion, and the transitive-pinning opt-out. Keep the existing analyzer regression tests on main instead of reintroducing duplicate copies from dotnet/dotnet#9157. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 42e15b55-755d-4c11-8413-c4bf270a9425
|
Resolved the unsafe backflow in merge commit 4ddf77628, applying VMR build 339485 ( VMR fixes retained
Conflict-resolution choicesPreserved main's 18.14 branding and API-compat baseline, Wave 18.14, current OptProf baseline and release documentation, and newer TaskAnalyzer diagnostic guidance. The incoming older snapshot was not allowed to downgrade or remove these changes. The final change is limited to six dependency/source-build metadata and project files. The source marker now records VMR build 339485, rather than the old build 329383. |
|
@JanProvaznik was the change to backflow from VMR 11.0.2xx instead of main intentional? I assume this changed recently as part of the release activities? |
|
yes this is intentional, it changed when VMR main became NET 12, so a month ago |
No dependency updates to commit [[ commit created by automation ]]
Caution
This is an unsafe codeflow update⚠️ Please review carefully as it may contain undesirable changes and/or reverts.
This PR is a self-corrective attempt most likely caused by a recent change in codeflow subscriptions which results in the currently flown branch
release/11.0.2xxbeing divergent from the previously flownmain.It may contain both source code changes from the VMR
as well as dependency updates. Learn more here.
If the changes in this PR look wrong, you also have the option to reset the VMR's contents to match the repository:
This pull request brings the following source code changes
From https://github.com/dotnet/dotnet
New Dependencies
Associated changes in source repos
Diff the source with this PR branch