mirror of
https://github.com/rudrankriyam/App-Store-Connect-CLI.git
synced 2026-04-25 15:45:48 +03:00
[GH-ISSUE #147] [feat] Add support for build-specific "What to Test" notes (betaBuildLocalizations) #32
Labels
No labels
bug
bug
documentation
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/App-Store-Connect-CLI#32
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mithileshchellappan on GitHub (Jan 25, 2026).
Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/147
Feature Request
Add support for managing TestFlight "What to Test" notes (test instructions shown to beta testers).
Problem
No way to add/manage test notes via CLI. Users must manually add them through App Store Connect web UI.
Proposed Solution
Two-part approach:
1. Add flags to upload commands
2. Add CRUD subcommand
Examples:
API Reference
Endpoints:
POST /v1/betaBuildLocalizations(create)PATCH /v1/betaBuildLocalizations/{id}(update)GET /v1/betaBuildLocalizations/{id}(get)GET /v1/builds/{id}/betaBuildLocalizations(list)DELETE /v1/betaBuildLocalizations/{id}(delete)Attributes:
whatsNew(string) - Test instructionslocale(string) - Locale code (e.g., "en-US")Docs: https://developer.apple.com/documentation/appstoreconnectapi/testflight/beta_build_localizations
Implementation Note
Test notes can only be added after build reaches
processingState: "VALID". When--test-notesis used, auto-wait for processing or require--waitflag.Use Case
Environment
ascversion:0.12.0@mithileshchellappan commented on GitHub (Jan 25, 2026):
I'll have a PR ready to push by tomorrow (if @rudrankriyam doesn't have claude push it by then 😅)
@rudrankriyam commented on GitHub (Jan 25, 2026):
Currently testing the implementation, should go live in the next version very soon