CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions

apple: release type (apple.releaseType, apple release --after-approval|--manual), device-family preflight, TestFlight invite needs an installable build

Browse source
This commit is contained in:
CRTkafa 2026-10-27 17:07:37 +07:00
parent 4763862178
commit 85cf494c0a
24 changed files with 899 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

5
skills/testflight/SKILL.md
View file

@ -39,7 +39,10 @@ changes or deletes a group.
commits; storebound masks them in every log line (`j***@example.com`).
- `storebound apple testflight testers --dry` shows: new testers, testers added to more groups, (with `--remove`)
testers who leave a managed group. The real run **asks first**: Apple emails each new tester an invitation once the
group has a build. `--invite` (re)sends invitations to testers still `NOT_INVITED` / `INVITED` (asks again).
group has a build. `--invite` (re)sends invitations to testers still `NOT_INVITED` / `INVITED` (asks again) once a build of the tester's group is
installable (an external group: past Beta App Review). Without one the tester is added, the invite is skipped and the run
says "tester added; the invite goes out when a build in <group> passes Beta App Review (re-run with --invite then)" (exit 0;
Apple's 409 `NO_INSTALLABLE_BUILDS` is handled the same way; `distribute --submit-review` prints the same line; pitfall 127).
- Internal groups only take App Store Connect users (Users and Access); add people there first.
- Testers are an owner action: not an MCP tool. An agent prepares the CSV format and the dry run, the owner runs it.