Bump trunk's VERSION_SHORT to 27.2

[mokagio]

Description

The TestFlight build steps on trunk have been failing for a few days because we keep producing 27.1 builds despite that version having been shipped.

This PR simply bumps the version on trunk to 27.2, which should address the TestFlight rejection. #25876 has a draft attempt at updating the release automation to account for the current shape of semi-continuous-deployment.

AI-generated details

27.1 shipped and Apple closed its pre-release train. Nothing bumps trunk between a release shipping and the next code freeze, so trunk still names a version App Store Connect will no longer accept, and every TestFlight upload from it is rejected:

[altool.C97045740] This bundle is invalid. The value for key CFBundleShortVersionString [27.1]
in the Info.plist file must contain a higher version than that of the previously approved
version [27.1]. (90062)

That is 18 consecutive trunk builds since #33637 on 6 August, both :testflight: jobs and both Prototype Build jobs on each. No internal build has reached testers in a week — and the nightly promotion job has been passing throughout while logging No build uploaded in the last 24h; nothing to promote to nightly, which is why this stayed quiet.

This is the one-line half of #25876, split out so it can land now. #25876 stays open for the release.rb change that pre-allocates the version automatically at finalization, which is the deferred half of the faster-releases RFC (pbArwn-7YT-p2) and wants a proper review.

VERSION_LONG is deliberately left at 27.1.0.4. code_freeze writes both fields onto the new release branch and then commits with allow_nothing_to_commit: false, so pre-setting VERSION_LONG to 27.2.0.0 here would leave that commit empty and fail the lane. Nothing reads it in the meantime — build_and_upload_app_for_testflight mints its build code as <marketing version>.0.<BUILDKITE_BUILD_NUMBER> and never touches VERSION_LONG. trunk carrying the previous release's build code is the existing steady state.

The only consequence for the next freeze is none: .buildkite/release-pipelines/code-freeze.yml already passes version:"${RELEASE_VERSION}" explicitly, so the release_version_next derivation is not consulted on CI.

Testing instructions

[dangermattic]

	1 Message
📖	This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

[Copilot]

Pull request overview

This PR updates the app’s marketing version on trunk to unblock TestFlight uploads now that the 27.1 pre-release train is closed in App Store Connect.

Changes:

• Bump VERSION_SHORT from 27.1 to 27.2 while intentionally leaving VERSION_LONG unchanged.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.