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

docs: update CLAUDE.md current version to 1.2.1 (1.2.0 shipped)

Browse Source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BkanrydYtrme8wipTzWssG
This commit is contained in:
alexandrev-tibco
2026-07-11 11:00:15 +02:00
parent 8ba8e4e933
commit 75cf7ebaad
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**: 1.1.5 - **Current version**: 1.2.1 (dev; 1.2.0 shipped to the App Store)
- **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 = 1.1.5` → active branch is `1.1.5`. 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 = 1.2.1` → active branch is `1.2.1`. Keep them in sync. (The build number bump within the same version does NOT rename the branch — only a version change does.)
## Credentials — all managed via `pass` (GPG-encrypted, syncs to Gitea) ## Credentials — all managed via `pass` (GPG-encrypted, syncs to Gitea)