alexandrev/FamilyMealPlanner
1
0
Fork 0
Code Issues 6 Pull Requests Packages Projects Releases Wiki Activity

docs: CLAUDE.md a version 2.0.4

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013H6bXqGX1ygwib1Dm3n3UG
This commit is contained in:
alexandrev-tibco
2026-08-23 13:42:47 +02:00
parent 9221ecb7e5
commit d41f72a84f
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CLAUDE.md
+2 -2
View File
@@ -4,7 +4,7 @@
- **Name**: MealMood: Family Meal Planner - **Name**: MealMood: Family Meal Planner
- **Bundle ID**: com.alexandrevazquez.mealmood - **Bundle ID**: com.alexandrevazquez.mealmood
- **Platform**: iOS/iPadOS (also runs as iOS app on Mac) - **Platform**: iOS/iPadOS (also runs as iOS app on Mac)
- **Current version**: 2.0.3 (dev, beta-bound; 2.0.2 shipped to the App Store 2026-08-19) - **Current version**: 2.0.4 (dev, beta-bound; 2.0.2 shipped to the App Store 2026-08-19)
- **Main branch**: `1.0.1` (production), feature branches named after versions - **Main branch**: `1.0.1` (production), feature branches named after versions
### Branch ↔ version convention (IMPORTANT) ### Branch ↔ version convention (IMPORTANT)
@@ -13,7 +13,7 @@ The active dev branch is named after the **current** `MARKETING_VERSION`, not th
# after bumping MARKETING_VERSION in the Xcode project to e.g. 1.1.6 # after bumping MARKETING_VERSION in the Xcode project to e.g. 1.1.6
git branch -m <old-version> 1.1.6 # e.g. git branch -m 1.1.5 1.1.6 git branch -m <old-version> 1.1.6 # e.g. git branch -m 1.1.5 1.1.6
``` ```
Right now: `MARKETING_VERSION = 2.0.3` → active branch is `2.0.3`. Keep them in sync. (The build number bump within the same version does NOT rename the branch — only a version change does.) Right now: `MARKETING_VERSION = 2.0.4` → active branch is `2.0.4`. Keep them in sync. (The build number bump within the same version does NOT rename the branch — only a version change does.)
**`MARKETING_VERSION` in the Xcode project does NOT drive the shipped version.** Both Info.plists hardcode their values, so bumping the project setting alone builds an IPA with the old version and App Store Connect rejects it (`90062: must contain a higher version than that of the previously approved version`). A version bump means editing three places, and `fastlane`'s `increment_build_number` only handles the app's build number: **`MARKETING_VERSION` in the Xcode project does NOT drive the shipped version.** Both Info.plists hardcode their values, so bumping the project setting alone builds an IPA with the old version and App Store Connect rejects it (`90062: must contain a higher version than that of the previously approved version`). A version bump means editing three places, and `fastlane`'s `increment_build_number` only handles the app's build number: