You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/ios/AGENTS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@ Root rules still apply. This file adds the iOS release guardrails.
5
5
## App Store Releases
6
6
7
7
- Agent-driven App Store uploads must use only `pnpm ios:release:upload`.
8
+
- App Store uploads must include explicit release intent: `pnpm ios:release:upload -- --version <YYYY.M.D>` and `--build-number <n>` when a specific build has been chosen.
8
9
- If `pnpm ios:release:upload` exits non-zero, stop immediately and report the failing step.
9
10
- After a failed `pnpm ios:release:upload`, do not continue with `pnpm ios:release:archive`, `asc builds upload`, `asc release stage`, `asc publish appstore`, `asc review submit`, direct Fastlane lanes, or any manual App Store Connect mutation command.
10
11
- Do not submit an iOS App Store version for App Review. App Review submission stays manual unless the user explicitly asks to submit a specific already-prepared version after the failed state has been reported.
Copy file name to clipboardExpand all lines: apps/ios/README.md
+25-30Lines changed: 25 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,13 +74,13 @@ Release behavior:
74
74
- The release archive is validated before upload by inspecting the exported IPA's signed entitlements, embedded App Store profile, and push mode. The upload fails if the IPA is not an App Store production relay build.
75
75
- App Review submission is manual in App Store Connect. The release lane uploads a build, public metadata, and the App Review PDF attachment, but it does not submit for review or upload the App Store Connect `Notes` field.
76
76
- The release flow does not modify `apps/ios/.local-signing.xcconfig` or `apps/ios/LocalSigning.xcconfig`.
77
-
-`apps/ios/version.json` is the pinned iOS release version source.
77
+
-Release uploads require an explicit CalVer version passed with `--version`.
78
78
-`apps/ios/CHANGELOG.md` is the iOS-only changelog and release-note source.
79
-
- The pinned iOS version must use CalVer like `2026.4.10`.
80
-
- That pinned value becomes:
79
+
- The release version must use CalVer like `2026.4.10`.
80
+
- That release value becomes:
81
81
-`CFBundleShortVersionString = 2026.4.10`
82
82
-`CFBundleVersion = next App Store Connect build number for 2026.4.10`
83
-
-Changing the root gateway version does not change the iOS app version until you explicitly pin from the gateway.
83
+
-Local defaults derive from root `package.json`; App Store uploads use the explicit `--version` value.
84
84
- See `apps/ios/VERSIONING.md` for the full workflow.
85
85
86
86
Relay behavior for App Store builds:
@@ -110,13 +110,13 @@ Release-owner secrets:
110
110
Prepare the generated release xcconfig/project without archiving:
@@ -166,25 +166,25 @@ This should create `apps/ios/fastlane/.env` with non-secret App Store Connect va
166
166
167
167
Use `pnpm ios:release:signing:setup` for the initial portal setup, then `MATCH_PASSWORD=... pnpm ios:release:signing:sync:push` to publish encrypted Fastlane match assets to the shared private repo.
168
168
169
-
4. If you are starting a brand-new production release train, pin iOS to the current gateway version first:
169
+
4. If you are starting a brand-new production release train, add or update the matching iOS changelog section and sync generated metadata:
0 commit comments