Repository navigation
🤖 Merge 'main' => 'xcode27.0' - #26149
Conversation
This pull request updates the following dependencies ## From https://github.com/dotnet/xharness - **Subscription**: [02e03784-16b3-4ced-b02a-3715797fc7da](https://maestro.dot.net/subscriptions?search=02e03784-16b3-4ced-b02a-3715797fc7da) - **Build**: [20260715.2](https://dev.azure.com/dnceng/internal/_build/results?buildId=3023105) ([322990](https://maestro.dot.net/channel/2/github:dotnet:xharness/build/322990)) - **Date Produced**: July 15, 2026 12:48:39 PM UTC - **Commit**: [6e3f7251a2d482f71f6e6c786ded8d3b80dae792](dotnet/xharness@6e3f725) - **Branch**: [main](https://github.com/dotnet/xharness/tree/main) - **Dependency Updates**: - From [11.0.0-prerelease.26360.1 to 11.0.0-prerelease.26365.2][1] - Microsoft.DotNet.XHarness.iOS.Shared [1]: dotnet/xharness@ab06ed6...6e3f725
The milestone-based filtering in the code-radiator workflow is supposed to skip target branches whose corresponding milestone is closed. It never did: PR #26125 was created for `xcode26.6` even though the `xcode26.6` milestone had been closed ~12 hours earlier. ## Root cause The workflow instructed the agent to run: ```bash gh api 'repos/{owner}/{repo}/milestones?state=closed&per_page=100' --paginate -q '.[].title' ``` But the agent runs in the gh-aw firewall sandbox where `gh` is **not authenticated** (the agent step env sets no `GH_TOKEN`/`GITHUB_TOKEN`; gh-aw even injects a prompt stating that `gh` is not authenticated and reads should go through the GitHub MCP server). Every invocation returned: ``` gh: To use GitHub CLI in a GitHub Actions workflow, set the GH_TOKEN environment variable... Error fetching milestones ``` The `|| echo "Error fetching milestones"` fallback swallowed the failure, so the agent saw an empty milestone list and processed every branch. This has been broken since the check was first added. Exposing a token to the agent container is blocked by gh-aw strict mode by design, and the pinned github-mcp-server (v1.4.0) has no milestone-list read tool. ## Fix Fetch the closed milestones in a trusted `pre-agent-steps` step that runs on the runner (which has a token), writing the titles to `/tmp/gh-aw/code-radiator/closed-milestones.txt`. The `/tmp/gh-aw` directory is bind-mounted read-write into the agent sandbox, so the agent reads the file directly. The step uses `set -euo pipefail` so a fetch failure hard-fails the run instead of being silently ignored. The milestone-filtering instructions now read that file instead of calling `gh`, and abort (creating no PRs) if the file is missing or unreadable. 🤖 Pull request created by Copilot --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…and 5 other types (#26122) Improve XML documentation for 7 types: - **CBCentralManager**: Remove empty nodes - **HKAnchoredObjectQuery**: Remove empty nodes - **INSearchCallHistoryIntent**: Remove empty nodes - **UIBezierPath**: Fix summary and remove empty nodes - **DraggingEventArgs**: Remove empty nodes - **UISearchController**: Remove empty nodes - **VNDetectBarcodesRequest**: Remove empty nodes Total: 30 changed lines (11 insertions, 19 deletions) 🤖 Pull request created by Copilot --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…#26076 (#26082) `RemoveUserResourcesSubStep` strips embedded MonoTouch/XamMac content/page resources (and native libraries listed in `[LinkWith]`) from user assemblies. To do so it upgrades the user assembly from `AssemblyAction.Copy` to `Save`, which re-serializes the assembly and breaks Hot Reload. ## Approach When `$(HotReloadCompatibleBuild)` is enabled, skip resource stripping for user (reloadable) assemblies. Since the step already only ever touches user assemblies, an early return at the top of `ModifyAssembly` cleanly "skips reloadable assemblies" and avoids the `Copy -> Save` upgrade, leaving the assembly byte-identical. Release builds don't enable the property, so their app size is unaffected. The embedded resources stay in the app for Hot Reload builds, a minor app-size cost limited to that configuration. The fix works in both compilation modes the step is built into (the `ExceptionalSubStep` used by the dotnet-linker and the `AssemblyModifierStep` used by the assembly-preparer); both expose `Configuration`. Fixes #26076 🤖 Pull request created by Copilot --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…6097) The Xcode version recommended for a given .NET for iOS/tvOS/macOS/Mac Catalyst build was only available as the internal `_RecommendedXcodeVersion` property, so there was no supported way for a project to read it. This makes it a public `RecommendedXcodeVersion` property and documents it (with a `dotnet build -getProperty:RecommendedXcodeVersion` example). The internal `_RecommendedXcodeVersion` property is still set (derived from the public one) in case anybody depends on it being set. Ref: #25818 🤖 Pull request created by Copilot --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Co-authored-by: Rolf Bjarne Kvinge <rokvin@microsoft.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…6041) Developers frequently can't find the `.dSYM` debug symbols after `dotnet publish`, because they're left in the build output directory (next to the `.app`) while the published `.ipa`/`.pkg` lands in the publish directory. This trips people up when they need to symbolicate crashes or upload symbols to a crash reporting service, and it's a recurring source of confusion in issue #15384. This change copies any generated `*.dSYM` directories into the publish directory during `dotnet publish`, so the debug symbols end up right alongside the published package. Fixes #15384 🤖 Pull request created by Copilot --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Protected files were modified in this pull request and require manual scrutiny before merge.
Please verify that each protected-file change is intentional, policy-compliant, and safe:
- Protected files:
README.md,.agents/files/training-log-macios-binding-creator.md,.agents/skills/macios-binding-creator/SKILL.md,.agents/skills/macios-binding-creator/references/binding-patterns.md,.agents/skills/macios-binding-creator/references/test-workflow.md,.agents/training-logs/macios-binding-creator.md
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
❌ [CI Build #e308684] Prepare .NET Release failed ❌The following jobs reported a non-successful result:
📦 Signed NuGet packages (32 packages)iOS
MacCatalyst
macOS
tvOS
Other
Pipeline on Agent |
✅ API diff for current PR / commitNET (empty diffs)✅ API diff vs stableNET (empty diffs)ℹ️ Generator diffGenerator Diff: vsdrops (html) vsdrops (raw diff) gist (raw diff) - Please review changes) Pipeline on Agent |
This comment has been minimized.
This comment has been minimized.
🚀 [CI Build #16515c3] Test results 🚀Test results✅ All tests passed on VSTS: test results. 🎉 All 195 tests passed 🎉 Tests counts✅ assembly-processing: All 1 tests passed. Html Report (VSDrops) Download macOS tests✅ Tests on macOS Sonoma (14): All 5 tests passed. Html Report (VSDrops) Download Linux Build VerificationPipeline on Agent |
Caution
Protected files were modified in this change.
This pull request is in
request_reviewmode and requires explicit human scrutiny before merge.Protected files:
README.md,.agents/files/training-log-macios-binding-creator.md,.agents/skills/macios-binding-creator/SKILL.md,.agents/skills/macios-binding-creator/references/binding-patterns.md,.agents/skills/macios-binding-creator/references/test-workflow.md,.agents/training-logs/macios-binding-creator.mdAutomated merge of
mainintoxcode27.0.Created by the code-radiator workflow.