docs: App Clip signing/provisioning for the release flow#714
Conversation
The ADE app embeds an App Clip (com.ade.ios.Clip, PR #706), so a manual-signing export must provision three bundles, not two. Document the minted 'ADE App Clip App Store' profile (+ re-mint command) and the auto-plist escape hatch in both AGENTS.md and the release skill's 7c gotchas, so a context-free release agent doesn't hit a surprise signing failure on the clip. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Warning Review limit reached
Next review available in: 46 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Documents the App Clip's release-signing requirement so a future context-free
/releaseagent doesn't hit a surprise signing failure.Why
The ADE app now embeds an App Clip (
com.ade.ios.Clip, PR #706). A manual-signing export (ExportOptions.plist) must provision three bundles — app, widgets, and clip. Neither AGENTS.md nor the release skill mentioned the clip, so an agent using the manual plist would fail at archive-export with a confusing signing error (the auto plist would silently succeed — a coin-flip depending on which path it picks).What
ADE App Clip App Store(bound to the same distribution certs as the app). No code — this is why it's not in the diff; recorded here for traceability.ExportOptions.auto.plistescape hatch.Doc-only; no code paths touched.
🤖 Generated with Claude Code
Greptile Summary
This PR documents the App Clip signing requirement for iOS release flows. The main changes are:
AGENTS.md.Confidence Score: 5/5
This looks safe to merge.
No blocking issues found in the changed documentation. The added bundle ids and profile mapping match the visible iOS export configuration.
No files need attention.
What T-Rex did
Important Files Changed
Reviews (1): Last reviewed commit: "docs: record App Clip signing/provisioni..." | Re-trigger Greptile