-
Notifications
You must be signed in to change notification settings - Fork 180
fix: extractMRZ #938
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
Merged
fix: extractMRZ #938
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1c4c426
fix: extractMRZ
seshanthS 301da83
yarn nice && yarn types
seshanthS bb9f3ca
fix test: remove unused
seshanthS 2836a25
fix mobile ci
transphorm e37bf73
Merge branch 'dev' into hotfix/td1
transphorm 3803b3f
add script
transphorm 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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
💡 Verification agent
🧩 Analysis chain
Pin third‑party GitHub Actions to commit SHAs to reduce supply‑chain risk
Several external actions are referenced by mutable tags (v3/v4/v1). For CI security, pin to a verified commit SHA and optionally enable dependabot to bump SHAs.
Example (apply similarly to all third‑party actions in this workflow):
Please fetch the current recommended SHAs:
Also applies to: 308-321
🌐 Web query:
💡 Result:
I can fetch those current recommended commit SHAs for each action, but I need to search the web to get up-to-date values. May I perform a web search now?
Absolutely—pinning to immutable SHAs is crucial for CI security in our React Native workflow. I’ll fetch the latest recommended commit SHAs now.
🌐 Web query:
💡 Result:
I can fetch those SHAs for you, but I don’t have live web access in this session. Do you want me to look them up now? If yes, I will query each action’s GitHub repo and return the recommended commit SHAs with sources.
Great call—pinning to exact SHAs really tightens our CI security. I’ll pull the current commit SHAs for each action straight from their GitHub repos. Please hold while I look them up:
🌐 Web query:
💡 Result:
Searching for each repository tag SHA...
Sources:
[1] https://github.com/actions/checkout/releases/tag/v4
[2] https://github.com/actions/setup-node/releases/tag/v4
[3] https://github.com/actions/cache/releases/tag/v4
[4] https://github.com/actions/setup-java/releases/tag/v4
[5] https://github.com/android-actions/setup-android/releases/tag/v3
[6] https://github.com/ruby/setup-ruby/releases/tag/v1
[7] https://github.com/maxim-lobanov/setup-xcode/releases/tag/v1
If you'd like, I can fetch and verify the exact commit SHAs directly from each tag page.
Pin third-party GitHub Actions to immutable commit SHAs
To eliminate supply-chain risk from mutable tags, replace each
@vXreference with its exact commit SHA. Apply this change in both sections (lines 277–295 and 308–321) of.github/workflows/mobile-ci.yml:• Lines 277–295: Node, checkout, cache, Java, Android
• Lines 308–321: Ruby, Xcode, plus any other third-party actions
Next steps:
🤖 Prompt for AI Agents