# Release Process

## Scope

A package release publishes iDevFlow tooling. It is distinct from an iOS app release and never grants push, archive/upload, App Store Connect, or tester-distribution authority.

## Maintainer checklist

1. Start from a clean `main` checkout.
2. Run `npm ci && npm run check`.
3. Run `IDEVFLOW_IOS_XCODE_E2E=1 IDEVFLOW_MACOS_XCODE_E2E=1 IDEVFLOW_UNIVERSAL_XCODE_E2E=1 npx tsx --test tests/xcode-e2e.test.ts`, then `IDEVFLOW_IOS_XCODE_E2E=1 npx tsx --test tests/real-app-handoff-e2e.test.ts`, on a supported macOS/Xcode installation.
4. Run `npx pi -e . --list-models`, `npm pack --dry-run --json`, and `git diff --check`.
5. Review `npm audit`; document any unavoidable transitive advisory in `docs/security.md`.
6. Verify config migrations from every previously supported schema and verify `idev_doctor report` contains no source/task/credential data.
7. Update the package version and changelog/release notes, commit, tag, and publish through the approved registry process.

## App handoff reminder

For an iOS candidate, `idev_release promote` changes only the local base branch after a candidate-bound approval. The manual TestFlight handoff package records the exact evidence and explicit next actions. A macOS handoff records distribution readiness without signing, archive, upload, notarization, or distribution. All external side effects remain separate manual operations.