chore: update fastlane to 2.232.0

[transphorm]

Description

A brief description of the changes, what and how is being changed.

Tested

Explain how the change has been tested (for example by manual testing, unit tests etc) or why it's not necessary (for example version bump).

How to QA

How can the change be tested in a repeatable manner?

Summary by CodeRabbit

• Chores
  • Updated deployment tooling to a newer stable release.
  • Updated build tool dependencies to latest stable versions.
  • Added a development-only dependency for automated dependency/security auditing to improve vulnerability checks during development and CI.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates app/Gemfile: bumps the fastlane gem from ~> 2.230.0 to ~> 2.232.0 and adds bundler-audit (~> 0.9) to the development group; no other code or configuration changes.

Changes

Cohort / File(s)	Summary
Gemfile changes app/Gemfile	Bumped fastlane constraint from ~> 2.230.0 to ~> 2.232.0; added bundler-audit (~> 0.9) to the development group.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update fastlane, enable local build bumps, and disable local Android uploads #1552: Also modifies app/Gemfile to update the fastlane dependency (related version bump).

Suggested labels

codex

Poem

✨ A tiny gem shift, tidy and neat,
Fastlane steps forward on nimble feet,
A new audit friend joins dev's parade,
Safe builds and smooth lanes quietly made. 🛠️

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is an unfilled template with placeholder text only; all required sections lack actual content about changes, testing, or QA procedures.	Replace placeholder text with actual details: describe the fastlane upgrade changes, explain why testing isn't needed (e.g., version bump), and clarify how to verify the update.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: updating fastlane to version 2.232.0, which aligns with the primary modification in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch justin/chore-update-fastlane-2_232_0

---

No actionable comments were generated in the recent review. 🎉

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@app/Gemfile`:
- Line 11: The Gemfile bump to fastlane (~> 2.232.0) can pull in a vulnerable
rexml transitively; inspect Gemfile.lock to verify the resolved rexml version is
>= 3.4.2, and if it is not, add/force the safe version by either running bundle
update fastlane rexml (or adding an explicit gem "rexml", ">= 3.4.2" to the
Gemfile) and then bundling to lock the safe version; also run bundler-audit (or
`bundle audit`) to scan for CVE-2025-58767 and other vulnerable transitive
dependencies and re-run your test suite after updating the lockfile to confirm
no regressions.