Skip to content

fix(ci): publish through private infrastructure - #5

Merged
m17kea merged 1 commit into
mainfrom
codex/dispatch-private-publisher
Jul 16, 2026
Merged

m17kea merged 1 commit into
mainfrom
codex/dispatch-private-publisher

Conversation

@m17kea

@m17kea m17kea commented Jul 15, 2026 •

Copy link
Copy Markdown

Context

The initial public-repository publisher queued indefinitely because the AWS-enabled ARC runner is not exposed to public repositories. Publishing must retain that security boundary.

TL;DR

Dispatch tested Symphony SHAs to a private publisher instead of running privileged jobs in the public repo.

Summary

  • Replace the public self-hosted build and deployment jobs with a scoped GitHub App dispatch.
  • Preserve automatic main publishing and validated manual retries.
  • Document the private publisher boundary and revised deployment chain.
  • Pair with activeviam/shared-infrastructure#7, which owns the privileged publisher.

Alternatives

  • Allowing public repositories on the AWS-enabled runner group was rejected as an unsafe trust expansion.
  • GitHub-hosted ARM builds were rejected because image promotion still requires private AWS credentials.

Test Plan

  • COLUMNS=240 LINES=60 make -C elixir all
  • actionlint -config-file .github/actionlint.yaml

Summary:
- replace public-repository self-hosted build jobs with a scoped dispatch
- document the private publisher trust boundary and deployment chain

Rationale:
- AWS-enabled self-hosted runners must not execute workflows from a public
  repository where untrusted forks can influence pull-request code
- the private GitOps repository can validate the tested SHA before building

Tests:
- COLUMNS=240 LINES=60 make -C elixir all
- actionlint -config-file .github/actionlint.yaml

Co-authored-by: Codex <codex@openai.com>
@m17kea
m17kea merged commit ee17d70 into main Jul 16, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant