Fix cross-target bundled CLI startup - #2379
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.
Summary
--versionandcommandswith native Sharp packages unavailable/varand/private/varaliases hash identicallyRefs #1250.
Testing
Passed:
npm run buildnpm run test:cli-build-freshnessnpm run test:release-targetnpm run test:sharp-release-runtimenpm run test:prepare-declaration-rebuildnpm run test:release-package-coverage(initial complete run)The full package smoke reaches an unrelated existing failure in
native-mariadb-runtime-service.test.ts: the loopback collision fixture allocates once instead of twice (1 !== 2). A repeated 430+ MB release-package run later timed out after the initial successful run.AI Assistance
OpenAI
gpt-5.6-solthrough OpenCode reproduced the packaged CLI failure, implemented the lazy native dependency boundary and macOS provenance normalization, and ran the listed verification. Chris Huber reviewed and remains responsible for the change.