[Kitenite]

1.2.1 (build 140) was approved and went live on 2026-11-08. App Store Connect refuses uploads to an approved version, so the next native merge to main would fail the upload job in deploy.yml. This bumps the marketing version in app.config.ts and store.config.js to 1.2.2 (see apps/mobile/RELEASE.md → Versioning).

fingerprint.config.js keeps the version out of the runtime fingerprint, so this does not force a native build or cut installed builds off from OTA updates. eas-runtime-version and fingerprint.config tests pass.

1.2.2 still owes App Review: #9434 (no billing link-outs, 3.1.1) and the voice-mode device recording (2.5.4).

---

Summary by cubic

Bumps the mobile marketing version to 1.2.2 so the next native merge doesn't fail the deploy job. 1.2.1 (build 140) went live on the App Store on 2026-11-08, and App Store Connect rejects uploads to an already-approved version.

The version change in app.config.ts and store.config.js is excluded from the runtime fingerprint, so it won't force a native build or cut installed builds off from OTA updates. 1.2.2 still owes App Review: #9434 (no billing link-outs, 3.1.1) and the voice-mode device recording (2.5.4).

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

Summary by CodeRabbit

• Chores
  • Updated the mobile app’s release version to 1.2.2 in its app and store release settings. No user-facing feature or behavior changes are included in this update.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The mobile app version changes from 1.2.1 to 1.2.2 in the Expo app configuration and Apple store configuration.

Changes: Mobile app version update

Layer / File(s)	Summary
Update mobile version values apps/mobile/app.config.ts, apps/mobile/store.config.js	The configured app version and Apple app version change from 1.2.1 to 1.2.2.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related PRs

• ParadevAI/Paradev#9324: Changes the same two version fields from 1.2.1 to 1.2.2.
• ParadevAI/Paradev#9335: Updates the same version configuration fields and describes a patch-version bump workflow.

Suggested reviewers: saddlepaddle

Merge Risk: Minimal · up to 00400

The app and Apple store versions consistently advance to 1.2.2 without an established compatibility regression. The change is mergeable after normal checks.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title states the main change: the mobile app version is bumped to 1.2.2 to start the next release after 1.2.1 went live on the App Store. It uses conventional commit format (chore(mobile)) and mat…
Description check		The description covers the what and why. It explains that 1.2.1 (build 140) is approved and live, that App Store Connect rejects uploads to an approved version, and that the marketing version in app.c…
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title states the main change: the mobile app version is bumped to 1.2.2 to start the next release after 1.2.1 went live on the App Store. It uses conventional commit format (chore(mobile)) and matches the two version-bump edits in app.config.ts and store.config.js.

Full details: Description check

Explanation

The description covers the what and why. It explains that 1.2.1 (build 140) is approved and live, that App Store Connect rejects uploads to an approved version, and that the marketing version in app.config.ts and store.config.js moves to 1.2.2. It also covers the runtime fingerprint impact and notes the pending App Review items. It has a What and why section, but it does not follow the template's headings, and the How I tested it section is missing. It only says that the eas-runtime-version and fingerprint.config tests pass. It gives no screenshots, which the template does not require for this change, and it does not use the template's section headings. The checklist is also absent. The change is a version bump with no user-visible behavior, so the missing sections are non-critical.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 2 files.

Finishing Touches

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: c5ac0619-70b0-4429-b94b-55ba8383d775

Commits

Reviewing files that changed from the base of the PR and between bf4b1cc and 0040056.

Files selected for processing: 2

• apps/mobile/app.config.ts
• apps/mobile/store.config.js

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 6 remain after this review.

[cubic-dev-ai]

No issues found across 2 files

Architecture diagram

sequenceDiagram
    participant DEV as Developer
    participant CI as GitHub Actions (deploy.yml)
    participant ASC as App Store Connect
    participant EXPO as Expo / EAS Build
    participant EAS as EAS Update Service
    participant APP as Installed Mobile App
    participant CONFIG as app.config.ts / store.config.js
    participant FP as fingerprint.config.js

    Note over DEV,APP: Mobile Versioning & Release Flow

    DEV->>CONFIG: Set marketing version to 1.2.2

    CONFIG-->>EXPO: Read version for build config
    CONFIG-->>CI: Read version for metadata upload

    CI->>EXPO: Trigger native build & metadata sync
    EXPO->>ASC: Upload build with version 1.2.2

    alt Version not previously approved (1.2.2)
        ASC-->>EXPO: Accept upload
    else 1.2.1 already live/approved
        ASC-->>EXPO: Reject upload (prevents duplicate)
    end

    Note over APP,EAS: Runtime Fingerprint & OTA Continuity

    EXPO->>FP: Compute runtime fingerprint
    FP->>FP: Exclude version from fingerprint hash
    FP-->>EXPO: Stable fingerprint (unchanged from 1.2.1)

    EAS->>APP: Check for OTA updates
    alt Fingerprint matches installed build
        APP-->>EAS: No native update needed
    else Fingerprint mismatch
        APP-->>EAS: Native update required
    end

    APP-->>APP: Runtime continues to run 1.2.1 build seamlessly

Loading

_{View guided diff | Turn on auto-fix | Re-trigger cubic}

[github-actions]

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

• ✅ Neon database branch

Thank you for your contribution! 🎉

[expo]

Preview update published for development build 2b8038dc (fingerprint e65ce637d4ee). Open the build on your phone and scan:

Update group aeba3a9c