-
-
Notifications
You must be signed in to change notification settings - Fork 473
ci: detect zapi packages via zapi.targets in native portability check #9644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
nflaig
merged 1 commit into
ChainSafe:nflaig/check-native-portability
from
lodekeeper:fix/native-portability-zapi-targets
Jul 10, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To make the target matching more robust and defensive, we should ensure that
zapiTargetis a string and perform case-insensitive matching with whitespace trimming. This prevents potential issues if targets inpackage.jsonhave accidental leading/trailing spaces or different casing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks — I'd rather keep the strict match here.
zapi.targetsare canonical target triples, and this check should match exactly what the build tooling consumes to name thezig-out/lib/*.nodeartifacts. Lower-casing/trimming would let a non-canonical entry (stray whitespace, odd casing) satisfy the check even though it isn't the exact triple — i.e. a false pass, which is worse than a false fail for a portability guard: a strict miss is immediately visible and fixable, whereas a lenient pass can hide a genuinely missing/misnamed binary (the regression this check exists to catch). It also keepshasZapiTargetconsistent with the strict matching inhasBundledPrebuild/optionalDependencyForTarget.On the type guard:
zapiTargetsis already guaranteed to be an array (Array.isArray(...) ? ... : []), andArray.prototype.includesreturnsfalsefor any non-string entry without throwing, so it's crash-safe as-is — thetypeofcheck is only needed to support the.trim()/.toLowerCase()calls, which I'm leaving out for the reason above.