You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a release orchestration entry point that starts a versioned Context Panel release across selected distribution channels from one commit.
Finish Line
One workflow dispatch coordinates selected release channels from one version and commit.
Current Status
State: Active
Next action: Draft workflow inputs and execution order with App Store Connect upload as the default Apple path.
Blocked by: None
Waiting for: None
Last verified: 2026-05-28.
Scope
In: New or revised GitHub Actions workflow, inputs for version/build/channel selection, calls to existing Release/App Store Connect upload jobs or reusable workflow extraction, status summary.
One workflow has explicit inputs for version, optional build_number, GitHub release channel, App Store Connect upload channel, optional TestFlight beta channel, and dry-run/export-only mode.
Both release channels use the same target SHA.
The default Apple path uploads to App Store Connect without enabling/requiring TestFlight beta distribution.
The workflow fails clearly when required secrets for selected channels are missing.
The workflow writes a concise run summary with release URL, artifacts, App Store Connect upload/build number, TestFlight beta opt-in state, and skipped channels.
Existing manual workflows are either reused safely, renamed, or documented as lower-level tools.
Relationships
Part of the release hardening parent plan.
Validation
Dispatch a dry run/export-only workflow.
Dispatch a real release/upload when approved.
Inspect Actions summary and artifacts.
Decisions
2026-05-28: Default Apple channel should be App Store Connect upload, not TestFlight beta distribution.
Open Questions
Should orchestration call reusable workflows, composite actions, or shared scripts?
Should partial channel success be allowed, or should any selected channel failure fail the full release?
Should the existing TestFlight workflow be renamed to avoid implying beta distribution when it mainly uploads to App Store Connect?
Objective
Add a release orchestration entry point that starts a versioned Context Panel release across selected distribution channels from one commit.
Finish Line
One workflow dispatch coordinates selected release channels from one version and commit.
Current Status
State: Active
Next action: Draft workflow inputs and execution order with App Store Connect upload as the default Apple path.
Blocked by: None
Waiting for: None
Last verified: 2026-05-28.
Scope
Acceptance Criteria
version, optionalbuild_number, GitHub release channel, App Store Connect upload channel, optional TestFlight beta channel, and dry-run/export-only mode.Relationships
Part of the release hardening parent plan.
Validation
Decisions
Open Questions
TestFlightworkflow be renamed to avoid implying beta distribution when it mainly uploads to App Store Connect?