Skip to content

experiment: Agent macOS 27 builds on Blacksmith (do not merge) - #1308

Closed
AnthonyRonning wants to merge 14 commits into
masterfrom
exp/macos27-blacksmith-metal
Closed

AnthonyRonning wants to merge 14 commits into
masterfrom
exp/macos27-blacksmith-metal

Conversation

@AnthonyRonning

@AnthonyRonning AnthonyRonning commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Experiment only — do not merge. Based on PR #1266 (Xcode 27.1 for the Apple lanes), which moved the Agent's macOS builds from Blacksmith to GitHub's xcode-27 image: Blacksmith's macOS 27 image lacks the Metal Toolchain for Xcode 27.1, and xcodebuild -downloadComponent MetalToolchain fails there ("Failed fetching catalog"). On GitHub's runner the Agent Dev build took about 40 min, against 12–15 on Blacksmith.

One workflow, .github/workflows/macos27-blacksmith-experiment.yml, with two arms:

  1. Imported Metal Toolchain. export-metal (GitHub xcode-27) exports Xcode 27.1's Metal Toolchain with xcodebuild -downloadComponent metalToolchain -exportPath. blacksmith-imported-metal (blacksmith-6vcpu-macos-27) imports it with xcodebuild -importComponent, compiles a probe shader, then runs a cold cargo build --workspace --all-targets of the Agent, which compiles gpui's Metal shaders.
  2. No Metal Toolchain. blacksmith-runtime-shaders (blacksmith-6vcpu-macos-27) runs a cold cargo clippy -p maple-agent-app --all-targets with gpui's runtime_shaders feature, which skips build-time shader compilation. That would be enough for PR check lanes.

test_nix_workflows.py (install count) and test_select_xcode.py (selector inventory) are updated only so the repository checks stay green.

Local validation: both tests pass with yq-go; actionlint passes on the new workflow; the pre-commit repo lane passed (569 tests).

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

AnthonyRonning and others added 13 commits October 24, 2026 22:48
Pristine copy of the crates.io release, without its standalone lockfile,
so the following commits show Maple's patches as reviewable diffs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tauri 2.12 pulls in tao 0.37, the first release with working single-window
UIScene support, which iOS 27 SDK builds require (UIKit aborts at launch
otherwise). It also carries the Xcode 27 fixes in tauri-cli and in the
Swift plugin entry points of log and opener.

- tauri 2.12.4, tauri-build/macros/codegen 2.7.3, tauri-runtime-wry 2.12.2,
  wry 0.57.0
- plugins: log 2.10.1, updater 2.14.0, opener 2.7.2, os 2.4.0, fs 2.7.1,
  dialog 2.8.3; deep-link and single-instance stay on their pins
- @tauri-apps/cli 2.12.3, @tauri-apps/api 2.12.4, JS plugins to match
- tao is patched from the vendored 0.37.1 copy instead of 0.35.2
- Android: Gradle wrapper 8.11.1 -> 8.14.3 (with its checksum); Tauri 2.12's
  Android library and plugins use the compilerOptions DSL, which needs
  Gradle 8.13+. AGP, Kotlin, SDK, NDK and JDK stay as they are.

All versions are at least seven days old (bunfig minimumReleaseAge).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tauri-apps/tao#1217 was closed by #1224, which only fixed the getType()
null case. tao 0.37 still unwraps getIntent/getAction and the ClipData and
EXTRA_STREAM conversions, so a null launch intent aborts the process across
JNI before tauri-plugin-deep-link sees OAuth or payment redirects. Re-apply
Maple's 0.35.2 patch minus the hunk upstream now covers; checked with
cargo check --target aarch64-linux-android.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tauri-cli 2.12 looks for target/.tauri/linuxdeploy-07333c6-<arch>.AppImage
instead of linuxdeploy-<arch>.AppImage. It no longer found the pinned
wrapper, so it downloaded an unpinned linuxdeploy and ran it with its
own embedded gtk plugin. That plugin sources /etc/os-release, which the
Nix /usr bind leaves dangling, and the AppImage step failed.

Install the wrapper under the new name. tauri-cli now rewrites its
embedded plugin scripts in the cache on every build, so stop writing
Maple's copies there; the wrapper never runs them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Apps built with the iOS 27 SDK must adopt the scene-based life cycle or
UIKit aborts at launch (_UIApplicationEvaluateRuntimeIssueForNoSceneLifecycleAdoption).
tauri-cli merges src-tauri/Info.ios.plist into the generated iOS plist, so
the manifest stays out of the shared Info.plist that macOS also uses.

One scene only: tao 0.37 creates a single WebView window, and any extra
scene iPad or iPhone Duo opened would have no WebView and render black.
The delegate is tao's TaoSceneDelegate. iOS 26 SDK builds behave the same
with the manifest, so this lands before the Xcode 27.1 bump.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Patch it from an in-tree copy so the next commit can fix its Swift entry
point for Xcode 27. The copy omits the crate's pnpm lockfile, the Gradle
cache files it ships and its build-generated permission files, which are
ignored the same way as in plugins/tauri-plugin-iap.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Xcode 27 release builds need @_cdecl plugin entry points to be public for
the Rust bindings to link; Tauri 2.12.3 did the same for its own Swift
package (tauri-apps/tauri#16130). Covers the in-tree IAP plugin and the
vendored Sign in with Apple plugin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the scene life cycle, UIKit hands a launch URL to the connecting scene's
connection options and never calls scene:openURLContexts: for it. tao 0.37
ignores those options, so a deep link that starts Maple (for example an OAuth
callback after iOS killed the app) never reached tauri-plugin-deep-link.

Backports tauri-apps/tao#1376 onto the vendored tao 0.37.1 (only the import
context differs from upstream dev).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
GitHub's xcode-27 image keeps Xcode 27.1 (27A9275) at
/Applications/Xcode_27.1_Release_Candidate.app, and its default is 27.0. Also
consider Xcode_<version>_*.app after the exact names; selection still
requires the pinned build and still skips beta installs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Xcode 27.1 (27A9275) brings the iOS 27.1 SDK and iPhone Duo support, and
App Store Connect requires the iOS 27 SDK from April 2027.

- apple-toolchain.json pins 27.1 / 27A9275 for the selector, the Nix shell
  and the cache keys.
- Builders move to blacksmith-6vcpu-macos-27 and GitHub-hosted jobs to
  xcode-27; the macos-26 images have no Xcode 27. Signing stays on
  GitHub-hosted runners.
- Agent CI's macOS jobs select the pinned Xcode instead of the runner
  default (27.0 on the xcode-27 image); the workflow lint now rejects
  macos-14 and macos-26 labels.
- The iOS ONNX Runtime build targets iOS 16.0 like the app: Xcode 27 only
  builds for deployment targets 15.0 and later. Its hash pins move to
  27A9275 from a local Xcode 27.1 build, and the dead 17F42 defaults go.
- Docs: runner labels and the pin; the StoreKit harness commands no longer
  select the removed Xcode 26.6. Drops the stale project.pbxproj.backup,
  which still targeted iOS 13.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- actionlint: allow the blacksmith-6vcpu-macos-27 and xcode-27 labels,
  which the pinned actionlint predates.
- test-canonical-macho: Xcode 27's ld sorts local absolute symbols, so
  both fixtures came out in the same order. Swap the entries to recreate
  the input-order variant older linkers emitted.
- Agent shell: link Rust with Xcode's clang as well. nixpkgs' ld64
  cannot read the macOS 27 SDK's .tbd stubs (they list arm64e.x1), so
  build scripts failed to link (_strerror_r undefined).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Research and Agent: stop stripping build scripts and proc-macros in
  release builds. rustc strips Apple outputs with rust-objcopy, which
  doesn't pad __LINKEDIT entries, so chained-fixup images (deployment
  target 12+) can end up with a 4-byte-aligned string table. macOS 27's
  dyld refuses such dylibs once they're linked against the macOS 27 SDK,
  so rustc could not load zerofrom-derive ("can't find crate").
  Executables aren't checked, so shipped binaries keep their current
  strip settings.
- Agent desktop build: build the macOS binary on GitHub's xcode-27
  image. gpui compiles Metal shaders, and Blacksmith's macOS 27 image has
  no Metal Toolchain for Xcode 27.1 and cannot download it (the
  MobileAsset catalog fetch fails on every attempt).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Experiment only, not for merge. Checks whether the Agent's macOS 27 work
can stay on Blacksmith instead of GitHub's xcode-27 image:

- Export Xcode 27.1's Metal Toolchain on GitHub xcode-27, import it on
  blacksmith-6vcpu-macos-27, compile a shader, then build the Agent
  workspace cold with compiled Metal shaders.
- Without any Metal Toolchain, run the Agent app clippy with gpui's
  runtime_shaders feature.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Experiment only. Checks that blacksmith-16vcpu-ubuntu-2404 and
blacksmith-32vcpu-ubuntu-2404 provision without a pre-created scale set,
and times a cold Agent clippy and test build on each size.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@AnthonyRonning
AnthonyRonning force-pushed the ci/xcode-27.1 branch 3 times, most recently from 1d97989 to 0929f37 Compare October 30, 2026 05:06
Base automatically changed from ci/xcode-27.1 to master October 30, 2026 05:26
@AnthonyRonning
AnthonyRonning deleted the exp/macos27-blacksmith-metal branch November 2, 2026 02:30
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.

1 participant