2.0.2: bump de version y release notes

Version en los tres sitios (Info.plist de app y widget + MARKETING_VERSION) y
widget adelantado a build 67, que es el que generara fastlane.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Ks8uUcMA9mjypVK7F2Pkt
This commit is contained in:
alexandrev-tibco
2026-08-13 14:03:14 +02:00
parent cfa9769a06
commit 87e8735621
10 changed files with 19 additions and 31 deletions
+2 -2
View File
@@ -4,7 +4,7 @@
- **Name**: MealMood: Family Meal Planner
- **Bundle ID**: com.alexandrevazquez.mealmood
- **Platform**: iOS/iPadOS (also runs as iOS app on Mac)
- **Current version**: 2.0.1 (dev, beta-bound; 2.0 shipped to the App Store 2026-07-28)
- **Current version**: 2.0.2 (dev, beta-bound; 2.0.1 shipped to the App Store 2026-08-13)
- **Main branch**: `1.0.1` (production), feature branches named after versions
### 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
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.1` → active branch is `2.0.1`. 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.2` → active branch is `2.0.2`. 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: