asc-build-lifecycle

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha c079831542f6 · 22 Oct 2026Report an issue or request a re-scan

• Publisherrudrankriyam GitHub organizationOwner of the repository this skill is read from
• Source folderrudrankriyam/app-store-connect-cli-skills/skills/asc-build-lifecycleThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdictc079831542f6A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.

---
name: asc-build-lifecycle
description: Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.
---

# asc build lifecycle

Use this skill to manage build state, processing, and retention.

## Find the right build
- Latest build:
  - `asc builds info --app "APP_ID" --latest --version "1.2.3" --platform IOS`
- Next safe build number:
  - `asc builds next-build-number --app "APP_ID" --version "1.2.3" --platform IOS`
  - The command scans the full processed-build history and in-flight uploads, then returns one greater than the highest positive numeric build number. Blank or non-numeric processed build numbers are skipped with a warning; if no usable number remains, it falls back to `--initial-build-number`.
- Recent builds:
  - `asc builds list --app "APP_ID" --sort -uploadedDate --limit 10`

## Inspect processing state
- `asc builds info --build-id "BUILD_ID"`

## Distribution flows
- Prefer end-to-end:
  - `asc publish testflight --app "APP_ID" --ipa "./app.ipa" --group "GROUP_ID" --wait`
  - `asc publish appstore --app "APP_ID" --ipa "./app.ipa" --version "1.2.3" --wait --submit --confirm`

## Cleanup
- Preview expiration:
  - `asc builds expire-all --app "APP_ID" --older-than 90d --dry-run`
- Apply expiration:
  - `asc builds expire-all --app "APP_ID" --older-than 90d --confirm`
- Single build:
  - `asc builds expire --build-id "BUILD_ID" --confirm`

## Notes
- `asc builds upload` uploads and commits an IPA or PKG. Use `asc publish` when
  the workflow must also distribute to TestFlight or stage an App Store release.
- For long processing times, use `--wait`, `--poll-interval`, and `--timeout` where supported.

Excerpt, first 1,723 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/rudrankriyam/app-store-connect-cli-skills
git -C app-store-connect-cli-skills checkout c079831542f6

Works in

1. 2026-10-22
   ✓SAFE B 89 / 100

   first audit · source c079831542f6

Questions about asc-build-lifecycle

• github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/s — the audited source at commit c079831542f6 and every finding aboveObserved · 22 Oct 2026

Spotted something wrong? Report a correction · Methodology