fix(release): restore macOS 27 binary compatibility - #108
Merged
Merged
Conversation
Bun 1.4.0 emitted invalid ad-hoc Mach-O signatures that macOS 27 rejects at launch. Build release artifacts with Bun 1.4.2, keep the matching type metadata in sync, and verify Darwin signatures during release smoke tests so malformed binaries cannot be published again.
albert20260301
suggested changes
Sep 16, 2026
albert20260301
left a comment
albert20260301
left a comment
Contributor
There was a problem hiding this comment.
Required: the new Darwin signature check exposes that the proposed Bun 1.4.2 pin still emits an invalid x64 artifact. Compile binary (altertable-darwin-x64) fails at codesign --verify --strict with invalid signature (code or signature have been modified).
Please update the release toolchain/remediation so both Darwin targets pass strict verification, then rerun CI. As written, this cannot restore macOS compatibility for the x64 binary.
Bun 1.4.2 still emits an invalid ad-hoc signature for the x64 target. Replace Bun's signature for both Darwin artifacts with the system codesign tool before strict verification so the ARM64 and Intel release paths share the same valid signing boundary.
albert20260301
approved these changes
Sep 16, 2026
redox
approved these changes
Sep 16, 2026
redox
pushed a commit
that referenced
this pull request
Sep 16, 2026
🤖 I have created a release *beep* *boop* --- ## [1.6.2](v1.6.1...v1.6.2) (2026-09-16) ### Bug Fixes * make authentication remediation safe for headless use ([#103](#103)) ([f3336a0](f3336a0)) * **release:** restore macOS 27 binary compatibility ([#108](#108)) ([de05fd0](de05fd0)) * return unhealthy exit statuses for diagnostic commands ([#104](#104)) ([96a8474](96a8474)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Member
|
@francoischalifour nice, I confirm it works now |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The macOS native CLI binaries in v1.6.1 can fail before the CLI starts on macOS 27. The release was built with Bun 1.4.0, whose
bun build --compileoutput for Darwin ARM64 had an invalid ad-hoc Mach-O signature.Earlier macOS releases may still launch the binary despite the malformed signature, which hid the defect during existing smoke tests. macOS 27 enforces the signature and terminates the executable at launch.
This is an upstream Bun defect, documented in oven-sh/bun#39764 and partially fixed upstream in oven-sh/bun#39837. Bun 1.4.2 produces a valid ARM64 signature but still produces an invalid x64 signature, so release correctness cannot depend on Bun's embedded signature.
What changed
Upgrade the pinned release toolchain from Bun 1.4.0 to Bun 1.4.2.
Upgrade
@types/bunand the lockfile to match the runtime toolchain.Replace Bun's embedded signature on both Darwin release targets with a deterministic ad-hoc signature:
Verify every Darwin artifact with
codesign --verify --strictbefore invoking--versionand--help.Add unit coverage proving signing and signature verification apply only to Darwin targets.
The npm runtime compatibility floor remains
bun >=1.1.0. The issue affects standalone compiled release binaries, not the JavaScript bundle run through a user-installed Bun runtime.Verification
--version, and--helppassed.--version, and--helppassed under Rosetta.