[saddlepaddle]

Summary

• Bump to 1.1.2 now that 1.1.1 (45) is in review. Once Apple approves a version, App Store Connect refuses more uploads to it, and deploy.yml uploads every native merge. Expo's app versions guide says to bump "when production build is submitted to the app stores". Skipping that step is why build 41's upload failed on 2026-09-18. RELEASE.md now includes the step.
• Keep versions out of the runtime fingerprint. fingerprint.config.js skips ExpoConfigVersions and keeps the default PackageJsonAndroidAndIosScriptsIfNotContainRun. Before this, the version was part of the fingerprint (1.1.1 → 9034c64, 1.1.2 → 783d93e), so every bump forced a native build and cut installed builds off from updates. Now 1.1.1 and 1.1.2 both hash to c8f184d.
• Review notes drop "does not link to a purchase page" and the Refresh button, to match what was submitted with 1.1.1.

One-time cost: the hash moves once, from build 45's 9034c64. After this merges, deploy.yml builds and uploads a 1.1.2 binary, and JS-only updates from main won't reach 1.1.1 installs until 1.1.2 ships. The version bump alone would have cost exactly the same.

Test plan

• eas fingerprint:generate --platform ios --environment production: without the config, 1.1.1 reproduces build 45's EAS-recorded 9034c64 exactly (same calculation as CI); 1.1.2 is 783d93e. With the config, both are c8f184d
• Biome passes on the changed files

---

Summary by cubic

Bumps the mobile app to 1.1.2 and keeps versions out of the runtime fingerprint so future version bumps no longer force a native build.

• App Store Connect refuses uploads to a version once it's approved, and deploy.yml uploads every native merge; build 41's upload failed on 2026-09-18 for exactly this reason.
• The version was previously an input to the fingerprint (1.1.1 → 397d86f, 1.1.2 → dfb3cdd); the new fingerprint.config.js skips ExpoConfigVersions, so both versions hash identically to 63273df.
• RELEASE.md documents the bump step, and the review notes drop the purchase-page and Refresh button lines to match the 1.1.1 submission.

One-time cost: the hash moves once, from build 45's 397d86f. After this merges, JS-only updates from main won't reach 1.1.1 installs until the 1.1.2 binary ships, which the version bump alone would have cost anyway.

^{Written for commit e2be4b6. Summary will update on new commits.}

Summary by CodeRabbit

• Updates
  • Updated the mobile app’s release version to 1.1.2.
• Documentation
  • Clarified the release checklist and versioning guidance, including when to update the patch version during app review.
  • Explained that updating the version does not require a native rebuild or interrupt updates for existing installs.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: fbce6726-1f16-4238-bd8c-f5d2b4b1f9d4

📥 Commits

Reviewing files that changed from the base of the PR and between aa285eb and e2be4b6.

📒 Files selected for processing (4)

• apps/mobile/RELEASE.md
• apps/mobile/app.config.ts
• apps/mobile/fingerprint.config.js
• apps/mobile/store.config.js

Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The mobile app and Apple store versions are updated to 1.1.2. Fingerprint configuration excludes two version-related sources. The release guide adds instructions to bump the patch version after submission for review and during the shipping process.

Changes

Mobile app version update

Layer / File(s)	Summary
Version bump and release procedure apps/mobile/fingerprint.config.js, apps/mobile/app.config.ts, apps/mobile/store.config.js, apps/mobile/RELEASE.md	The app and store versions change to 1.1.2. The Payments review note is edited. Fingerprint configuration excludes two sources. The release guide explains when to bump the patch version and adds a shipping runbook step.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Suggested reviewers: kitenite

Merge Risk: ⚪ Minimal · up to e2be4

This change starts mobile version 1.1.2 and keeps version bumps from changing the runtime fingerprint, so JS updates continue to reach installed builds. Deployment still uploads a new binary only after a native build. No remaining issue blocks the merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 3…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title follows conventional commit format and clearly summarizes the version bump and fingerprint change.
Description check	✅ Passed	The description explains the changes and rationale, and provides a detailed test plan. It omits the template’s checklist and includes an autogenerated summary with fingerprint values that conflict wit…

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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.}

[expo]

No installed development build can load this pull request as an update: its native fingerprint is 63273df0c28c and no development build has it. Add the mobile-build label to build one.

[github-actions]

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

• ✅ Neon database branch

Thank you for your contribution! 🎉