Skip to content

fix(build): cross-platform pkg binaries via --no-bytecode (#132)#143

Merged
thiagoralves merged 2 commits into
mainfrom
development
Jun 1, 2026
Merged

fix(build): cross-platform pkg binaries via --no-bytecode (#132)#143
thiagoralves merged 2 commits into
mainfrom
development

Conversation

@thiagoralves

Copy link
Copy Markdown
Contributor

Promote the cross-platform binary fix to main (PR #142) so the v0.4.21 release can be re-triggered.

The prior v0.4.21 build produced all binaries but the cross-built Windows .exe crashed (V8 rejected Linux-built bytecode); smoke-windows blocked the release, so nothing was published. This adds --no-bytecode --public-packages "*" --public to every pkg call.

After merge, the v0.4.21 tag will be re-created on this commit to kick the release.

🤖 Generated with Claude Code

thiagoralves and others added 2 commits June 1, 2026 07:21
The v0.4.21 release built all binaries but the Windows .exe crashed at
launch: "[pkg] V8 rejected the bytecode cache ... mismatched host/target
V8 (cross-platform bytecode)". The Windows binary is cross-compiled on
Linux, and pkg's default V8 bytecode is not portable across host/target
platforms; @yao-pkg's newer V8 rejects it at runtime.

Add `--no-bytecode --public-packages "*" --public` to every pkg
invocation (release.yml x5, ci.yml binary-smoke, package.json build:pkg*)
so the snapshot ships plain JS instead of platform-specific bytecode.
Fine for a GPL project. The new smoke-windows job caught this before any
release was published (create-release was skipped).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…build

fix(build): disable pkg V8 bytecode for cross-platform binaries (#132)
@thiagoralves thiagoralves merged commit f4a3542 into main Jun 1, 2026
6 checks passed
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