chore(version): bump to 0.0.3#87
Merged
Merged
Conversation
Bump MARKETING_VERSION 0.0.2 -> 0.0.3 and CURRENT_PROJECT_VERSION 1 -> 2 across all targets (app + network extension must match for App Store) for the next TestFlight build carrying the merged dual-backend + CallKit fixes. Build 2 is a unique, monotonic build so TestFlight accepts the upload. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Greptile SummaryBumps the app version from
Confidence Score: 5/5Safe to merge — this is a mechanical version bump with no logic changes. All build configurations (app, network extension, test targets, both Debug and Release) have been updated consistently. The VERSION file matches the new MARKETING_VERSION. No code, entitlements, or capabilities were touched. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[project.pbxproj] --> B[App Target - Debug]
A --> C[App Target - Release]
A --> D[ColumbaNetworkExtension - Debug]
A --> E[ColumbaNetworkExtension - Release]
A --> F[ColumbaNetworkExtension - Staging variants]
A --> G[Test Targets]
B --> H["MARKETING_VERSION: 0.0.2 → 0.0.3\nCURRENT_PROJECT_VERSION: 1 → 2"]
C --> H
D --> H
E --> H
F --> I["MARKETING_VERSION: 0.0.2 → 0.0.3\nCURRENT_PROJECT_VERSION: 1 → 2"]
G --> J["CURRENT_PROJECT_VERSION: 1 → 2"]
K[VERSION file] --> L["0.0.2 → 0.0.3"]
Reviews (2): Last reviewed commit: "chore(version): bump /VERSION to 0.0.3 (..." | Re-trigger Greptile |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
ci_post_clone.sh drives MARKETING_VERSION from /VERSION (and the build number from the commit count), so the pbxproj edit alone never shipped 0.0.3 to TestFlight. Bump /VERSION too -- this is the field that actually lands. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the app to 0.0.3 for the next TestFlight build (carrying the merged dual-backend work + CallKit
voipfix + timestamp clamp).How versioning actually works here
ci_scripts/ci_post_clone.shis the source of truth on Xcode Cloud:MARKETING_VERSION← contents of/VERSIONCURRENT_PROJECT_VERSION←git rev-list --count HEAD(auto-incrementing build number)It rewrites the pbxproj on every CI build, so editing the pbxproj alone never ships a new version. This PR therefore bumps
/VERSION→0.0.3(the field that actually lands on TestFlight) and also bumps the pbxprojMARKETING_VERSION→0.0.3so local (non-CI) builds match.VERSION:0.0.2→0.0.3MARKETING_VERSION:0.0.2→0.0.3(local-build consistency; CI overrides from/VERSIONanyway)CURRENT_PROJECT_VERSION: bumped for local builds; CI sets it from the commit count (currently ~382)