[GH-ISSUE #84] Add phased release management for app versions #26

Closed
opened 2026-02-26 21:32:51 +03:00 by kerem · 0 comments
Owner

Originally created by @rudrankriyam on GitHub (Jan 24, 2026).
Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/84

Summary

Add App Store phased release management for app store versions.

API Endpoints

  • POST /v1/appStoreVersionPhasedReleases
  • PATCH /v1/appStoreVersionPhasedReleases/{id}
  • DELETE /v1/appStoreVersionPhasedReleases/{id}
  • GET /v1/appStoreVersions/{id}/appStoreVersionPhasedRelease
  • GET /v1/appStoreVersions/{id}/relationships/appStoreVersionPhasedRelease

Proposed CLI (brainstorm)

asc versions phased-release get --version VERSION_ID
asc versions phased-release create --version VERSION_ID --start-date YYYY-MM-DD --state ACTIVE
asc versions phased-release update --id PHASED_ID --state PAUSED|ACTIVE|COMPLETE
asc versions phased-release delete --id PHASED_ID --confirm

Behavior (brainstorm)

  • Mirror API fields exactly (state, startDate, etc.).
  • Allow updating state without changing dates.
  • Validate date format and state enum locally.

Implementation Plan

  1. internal/asc/phased_release.go with types + client methods.
  2. Add subcommands under versions.
  3. Add output formatting for phased release objects.

Tests

  • CLI validation for required flags and enum checks.
  • Client HTTP tests for POST/PATCH/DELETE.

Acceptance Criteria

  • CRUD for phased release linked to a version.
  • JSON output by default; table/markdown supported.
Originally created by @rudrankriyam on GitHub (Jan 24, 2026). Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/84 ## Summary Add App Store phased release management for app store versions. ## API Endpoints - `POST /v1/appStoreVersionPhasedReleases` - `PATCH /v1/appStoreVersionPhasedReleases/{id}` - `DELETE /v1/appStoreVersionPhasedReleases/{id}` - `GET /v1/appStoreVersions/{id}/appStoreVersionPhasedRelease` - `GET /v1/appStoreVersions/{id}/relationships/appStoreVersionPhasedRelease` ## Proposed CLI (brainstorm) ``` asc versions phased-release get --version VERSION_ID asc versions phased-release create --version VERSION_ID --start-date YYYY-MM-DD --state ACTIVE asc versions phased-release update --id PHASED_ID --state PAUSED|ACTIVE|COMPLETE asc versions phased-release delete --id PHASED_ID --confirm ``` ## Behavior (brainstorm) - Mirror API fields exactly (state, startDate, etc.). - Allow updating state without changing dates. - Validate date format and state enum locally. ## Implementation Plan 1) `internal/asc/phased_release.go` with types + client methods. 2) Add subcommands under `versions`. 3) Add output formatting for phased release objects. ## Tests - CLI validation for required flags and enum checks. - Client HTTP tests for POST/PATCH/DELETE. ## Acceptance Criteria - CRUD for phased release linked to a version. - JSON output by default; table/markdown supported.
kerem closed this issue 2026-02-26 21:32:52 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/App-Store-Connect-CLI#26
No description provided.