Skip to content

ci(srtla): dispatch-only publish + standardize apt-reindex payload - #30

Merged
andrescera merged 4 commits into
mainfrom
feat/apt-publishing
Jun 17, 2026
Merged

ci(srtla): dispatch-only publish + standardize apt-reindex payload#30
andrescera merged 4 commits into
mainfrom
feat/apt-publishing

Conversation

@andrescera

Copy link
Copy Markdown
Member

What

  • Remove R2 upload from publish-release.yml (apt-worker is now the sole R2 publisher)
  • Add apt-reindex dispatch with 5-key standard payload: {component:"srtla",repo:"srtla",channel,tag,version}
  • Fix indentation of dispatch step (YAML parse error corrected)

Why

The srtla publish workflow previously uploaded .debs directly to R2 and regenerated APT metadata per-repo. This is retired in favor of the centralized apt-worker sole-publisher model, which eliminates per-repo index races and centralizes signing.

How to verify

  • grep -E 'aws s3|R2_|--clearsign' .github/workflows/publish-release.yml → ZERO
  • grep client-payload .github/workflows/publish-release.yml → 5 keys including repo:"srtla" and tag
  • python3 -c "import yaml; yaml.safe_load(open('.github/workflows/publish-release.yml'))" → valid

Risks

Low. The R2 upload removal is safe since apt-worker handles all R2 uploads. The dispatch step is gated on the GitHub Release creation (G-A guardrail).

Move APT index ownership to the central apt-worker reindex. The publish job
now uploads only the receiver srtla_rec .deb to R2 and fires an apt-reindex
repository_dispatch instead of regenerating and GPG-signing Packages/Release
per-repo per-arch (which raced across repos). The .deb stays receiver-only
(srtla_send is excluded from install per ADR-003).
@andrescera
andrescera merged commit 45a2c28 into main Jun 17, 2026
4 checks passed
@andrescera
andrescera deleted the feat/apt-publishing branch June 17, 2026 00:11
@andrescera
andrescera restored the feat/apt-publishing branch June 17, 2026 04:52
@andrescera
andrescera deleted the feat/apt-publishing branch July 17, 2026 17:46
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