fix: Lock ruby version to 3.1.6 and bump pod to 1.16.2

[Cal-L]

Description

This bumps and locks pod version to 1.16.2. It also locks ruby to 3.1.6

Related issues

Fixes:

Manual testing steps

1. Run yarn setup
2. Steps should be successful
3. App should run normally

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
gem/[email protected]	environment, eval, filesystem, network, shell, unsafe	+33	14.4 MB

🚮 Removed packages: gem/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Network access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Network access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Network access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Network access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫
Shell access	gem/[email protected]	Location: Package overview	ios/Gemfile.lock	🚫

View full report↗︎

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore gem/[email protected]
• @SocketSecurity ignore gem/[email protected]
• @SocketSecurity ignore gem/[email protected]
• @SocketSecurity ignore gem/[email protected]
• @SocketSecurity ignore gem/[email protected]
• @SocketSecurity ignore gem/[email protected]
• @SocketSecurity ignore gem/[email protected]
• @SocketSecurity ignore gem/[email protected]

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 1e22391
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/f1f3836a-f85b-4ef0-acfd-cbbfca0703d9

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chrisleewilcox]

LGTM