chore(app): bump version to 1.0.528+788

[beastoin]

Bump app version for TestFlight/internal testing release with clock skew detection (#5929).

1.0.527+786 → 1.0.528+788

After merge, tag with v1.0.528+788-mobile-cm to trigger Codemagic build.

---

by AI for @beastoin

[beastoin]

lgtm

[greptile-apps]

Greptile Summary

This PR bumps the Flutter app version from 1.0.527+786 to 1.0.528+788 in app/pubspec.yaml for a TestFlight/internal testing release containing the clock skew detection feature from #5929.

• Single-file change: version string updated in app/pubspec.yaml
• The patch version increments by 1 (527 → 528) as expected
• The build number increments by 2 (786 → 788, skipping 787) — worth confirming this is intentional and not an artifact of the bump script

Confidence Score: 5/5

• This PR is safe to merge — it is a routine version bump with a single-line change.
• The change is minimal and mechanical: one line in pubspec.yaml. The only minor curiosity is the build number skipping 787, but this does not affect functionality and is a common occurrence when a prior draft build was discarded. No logic, dependencies, or behavior is affected.
• No files require special attention.

Important Files Changed

Filename	Overview
app/pubspec.yaml	Version bumped from 1.0.527+786 to 1.0.528+788; build number increments by 2 (skips 787), which may be intentional.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR merged to main] --> B["Tag: v1.0.528+788-mobile-cm"]
    B --> C[Codemagic CI triggered]
    C --> D[Build iOS app\n1.0.528 build 788]
    D --> E[Upload to TestFlight]
    E --> F[Internal testing\nwith clock skew detection]

Loading

_{Reviews (1): Last reviewed commit: "chore(app): bump version to 1.0.528+788" | Re-trigger Greptile}

[greptile-apps]

Build number skips 787

The build number increments from 786 to 788, skipping 787. This is unusual for a sequential version bump. If 787 was intentionally reserved or used for an internal/discarded build, this is fine — but it's worth confirming this is expected and not an off-by-one error in the bump script.