Skip to content

Restore Intel compatibility for release artifacts#46

Merged
lzhgus merged 2 commits intomainfrom
chore/issue-23-intel-launch-investigation
Apr 15, 2026
Merged

Restore Intel compatibility for release artifacts#46
lzhgus merged 2 commits intomainfrom
chore/issue-23-intel-launch-investigation

Conversation

@lzhgus
Copy link
Copy Markdown
Owner

@lzhgus lzhgus commented Apr 15, 2026

Summary

  • force the release archive step to build a universal macOS app (arm64 + x86_64)
  • add a CI guard that fails the workflow if the archived app binary is not universal
  • keep the existing signing/notarization flow intact

Root cause

Issue #23 happened because the release workflow archived on Apple Silicon without an explicit generic macOS destination or universal arch override. That allowed GitHub release artifacts to be published as arm64-only app bundles, which Finder rejects on Intel Macs with “this application is not supported on this Mac.”

Impact

  • future release artifacts should launch on Intel Macs that meet the existing macOS 15 requirement
  • CI will now catch architecture regressions before a release is published

Validation

  • xcodebuild -project Capso.xcodeproj -scheme Capso -configuration Release -destination 'generic/platform=macOS' -showBuildSettings
  • xcodebuild build -project Capso.xcodeproj -scheme Capso -configuration Release -destination 'generic/platform=macOS' -derivedDataPath build/DerivedData-universal CODE_SIGNING_ALLOWED=NO CODE_SIGNING_REQUIRED=NO ARCHS='arm64 x86_64' ONLY_ACTIVE_ARCH=NO
  • verified resulting binary with file and lipo -info

Closes #23

lzhgus and others added 2 commits April 14, 2026 20:42
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Release builds were being archived on Apple Silicon without an
explicit generic macOS destination, which allowed arm64-only app
bundles to be published. The workflow now forces a universal build
for release artifacts and fails fast if the archived app does not
contain both arm64 and x86_64 slices.

Constraint: Release packaging must continue using the existing signing and notarization flow
Rejected: Lower macOS deployment target | Intel launch failure was caused by architecture, not OS minimum version
Confidence: high
Scope-risk: narrow
Reversibility: clean
Directive: Keep the lipo verification in CI so Intel support cannot silently regress
Tested: xcodebuild -showBuildSettings with generic/platform=macOS confirmed ARCHS=arm64 x86_64 and ONLY_ACTIVE_ARCH=NO; unsigned Release build produced a universal Capso binary verified with file and lipo
Not-tested: End-to-end signed GitHub Actions release archive, notarization, and Intel hardware launch after release publishing
@lzhgus lzhgus marked this pull request as ready for review April 15, 2026 05:14
@lzhgus lzhgus merged commit 6c7d0f5 into main Apr 15, 2026
5 checks passed
@lzhgus lzhgus deleted the chore/issue-23-intel-launch-investigation branch April 15, 2026 05:14
@lzhgus lzhgus changed the title [codex] Restore Intel compatibility for release artifacts Restore Intel compatibility for release artifacts Apr 15, 2026
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.

[Bug] macos intel

1 participant