Repository navigation
[fix]: refresh ARM64 emulation before sandbox releases - #7764
Merged
Merged
Conversation
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
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.
What is this contribution about?
The multi-architecture sandbox release failed when Node 26.10.0 started npm under the runner's preinstalled ARM64 emulator: QEMU raised an illegal-instruction signal and exited 132. Register fresh ARM64 emulation before Buildx and reset the existing handler. Add a read-only PR check that builds the Dockerfile's Node stage and exercises Node and npm under ARM64 emulation.
How did you verify your code works?
The new Ubuntu ARM64 Node/npm smoke check passes. All PR checks are green. Using the CI-pinned Bun 1.3.14,
bun run verify --parallel=2passes formatting, lint, unused-code checks and all 10,295 tests across 996 files. The default-parallel runs hit timing assertions in unchanged tests; the final run uses the same full suite and assertions with a two-worker resource cap.Both YAML files parse and all embedded shell blocks pass syntax checks. The installed actionlint input metadata is stale for the new emulator action; its
resetinput was verified against the exact upstream v4 schema. The patch changes only the release workflow and its smoke check; it does not change the image's Node version, runtime code, signing or deployment conditions.How to Test
node --versionandnpm --versioncomplete.Migration Notes
This repairs the failed publication of the current sandbox version. No image version bump is included. A workflow-only merge does not trigger the existing release path filter, so publication must be dispatched after checks pass.
Review Checklist