fix: pin Bun to v1.3.11 to fix broken darwin-arm64 release binaries#280
Merged
fix: pin Bun to v1.3.11 to fix broken darwin-arm64 release binaries#280
Conversation
Bun v1.3.12 introduced a regression (oven-sh/bun#29120) where `bun build --compile` produces darwin-arm64 binaries with a truncated code signature. macOS requires all arm64 binaries to be at least ad-hoc signed, so the unsigned binary is immediately killed with SIGKILL (exit 137). Root cause: The Bun runtime binary grew by ~337KB in v1.3.12 (due to Zig compiler changes), triggering a latent bug in `macho.zig`'s `sig_size` calculation. The LC_CODE_SIGNATURE space allocated is too small for the actual SuperBlob — 196,592 bytes allocated vs 537,138 bytes needed — resulting in a truncated, invalid signature. Evidence: - v4.1.2 (working): built with Bun v1.3.11 (CI run #24075809811) - v4.1.3 (broken): built with Bun v1.3.12 (CI run #24285207021) - v4.1.4 (broken): built with Bun v1.3.12 (CI run #24296958808) - Locally confirmed: `codesign --remove-signature && codesign -s -` restores the binary to working state Pin to v1.3.11 until the upstream fix lands. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
latestto1.3.11in both CI and npm-publish workflows to fix broken darwin-arm64 release binariesProblem
Since v4.1.3, the released
ccmanagerbinary silently exits on macOS arm64 (Apple Silicon) without doing anything. This affects both v4.1.3 and v4.1.4 releases.Root Cause
Bun v1.3.12 introduced a regression (oven-sh/bun#29120) where
bun build --compileproduces darwin-arm64 binaries with a truncated code signature.The Bun runtime binary grew by ~337KB in v1.3.12 (due to Zig compiler changes), triggering a latent bug in
macho.zig'ssig_sizecalculation:Signature=adhoccode object is not signed at allmacOS requires all arm64 binaries to be at least ad-hoc signed. The unsigned binary is immediately killed with SIGKILL (exit 137). The
bin/cli.jswrapper then swallows this error silently (sinceerror.statusisnull, notundefined, it callsprocess.exit(null)→ exit code 0).Evidence
codesign --remove-signature && codesign -s -on the broken binary restores it to working stateTest plan
ccmanagerruns on macOS arm64🤖 Generated with Claude Code