Package archied/archie-gateway/archie-state-store/archie-playbooks as a linux/amd64 distribution zip in deploy.yml #1148

Closed
opened 2026-10-27 13:39:13 +00:00 by sam · 0 comments
Owner

deploy.yml currently only builds and pushes the archied and archie-agent
Docker images to GHCR. archie-gateway, archie-state-store, and
archie-playbooks are real standalone binaries (see cmd/) with no
distribution path at all outside task build from source -- surfaced
while closing out archie-core-8cda.4.7's "update CI/release artifacts"
item.

archie-agent is deliberately excluded: it never runs as a host binary,
only inside the container image the daemon spawns per task -- it stays
Docker-image-only exactly as it is today.

Scope, as agreed with Sam:

  • linux/amd64 only. No macOS/arm64 -- no server use case for it.
  • Ride the existing archied/vX.Y.Z tag (the deploy.yml job that already
    builds archied's Docker image), not a new independently-versioned
    release train. archie-gateway/archie-state-store/archie-playbooks
    aren't in tools/release.sh's two-component split and don't need to be
    for this -- they just ship at whatever archied's version is.

Acceptance criteria

  • On a push carrying an archied/vX.Y.Z tag, deploy.yml cross-compiles
    archied, archie-gateway, archie-state-store, and archie-playbooks for
    linux/amd64 and produces one zip archive as a build artifact/release
    asset (archie-core-archied-vX.Y.Z-linux-amd64.zip or similar).
  • The zip also contains: INSTRUCTIONS.md (new -- how to lay the binaries
    out, which deployments/*.toml profile to start from, and the
    systemd-user-service.md pointer), README.md, and CHANGELOG.md /
    CHANGELOG.archied.md / CHANGELOG.archie.md.
  • archie-agent is NOT included -- it stays Docker-image-only.
  • A gateway-only release (RUNTIME=skip) still produces the zip; the zip
    is keyed to the archied tag only and doesn't depend on an archie-agent
    release.
  • task check / existing deploy.yml gate steps still pass; no change to
    the archied/archie-agent Docker image jobs.

Close reason

Landed in commit d687f05: new dist-zip job in .github/workflows/deploy.yml, triggered on archied/v* tags, packages archied/archie-gateway/archie-state-store/archie-playbooks (linux/amd64, CGO_ENABLED=0) plus deployments/INSTRUCTIONS.md and the CHANGELOG*.md files into one zip artifact. archie-agent excluded per scope. Verified locally: all four binaries build clean under the exact GOOS/GOARCH/CGO_ENABLED/ldflags the workflow uses, and the assembled zip's contents match. README.md omitted (copied only if present) since it doesn't exist in this repo yet.


Imported from beads archie-core-8cda.4.7.1 · GitHub #777 · type task · priority P2 · created 2026-09-07 · closed 2026-09-07

deploy.yml currently only builds and pushes the archied and archie-agent Docker images to GHCR. archie-gateway, archie-state-store, and archie-playbooks are real standalone binaries (see cmd/) with no distribution path at all outside `task build` from source -- surfaced while closing out archie-core-8cda.4.7's "update CI/release artifacts" item. archie-agent is deliberately excluded: it never runs as a host binary, only inside the container image the daemon spawns per task -- it stays Docker-image-only exactly as it is today. Scope, as agreed with Sam: - linux/amd64 only. No macOS/arm64 -- no server use case for it. - Ride the existing archied/vX.Y.Z tag (the deploy.yml job that already builds archied's Docker image), not a new independently-versioned release train. archie-gateway/archie-state-store/archie-playbooks aren't in tools/release.sh's two-component split and don't need to be for this -- they just ship at whatever archied's version is. ### Acceptance criteria - On a push carrying an archied/vX.Y.Z tag, deploy.yml cross-compiles archied, archie-gateway, archie-state-store, and archie-playbooks for linux/amd64 and produces one zip archive as a build artifact/release asset (archie-core-archied-vX.Y.Z-linux-amd64.zip or similar). - The zip also contains: INSTRUCTIONS.md (new -- how to lay the binaries out, which deployments/*.toml profile to start from, and the systemd-user-service.md pointer), README.md, and CHANGELOG.md / CHANGELOG.archied.md / CHANGELOG.archie.md. - archie-agent is NOT included -- it stays Docker-image-only. - A gateway-only release (RUNTIME=skip) still produces the zip; the zip is keyed to the archied tag only and doesn't depend on an archie-agent release. - task check / existing deploy.yml gate steps still pass; no change to the archied/archie-agent Docker image jobs. ### Close reason Landed in commit d687f05: new dist-zip job in .github/workflows/deploy.yml, triggered on archied/v* tags, packages archied/archie-gateway/archie-state-store/archie-playbooks (linux/amd64, CGO_ENABLED=0) plus deployments/INSTRUCTIONS.md and the CHANGELOG*.md files into one zip artifact. archie-agent excluded per scope. Verified locally: all four binaries build clean under the exact GOOS/GOARCH/CGO_ENABLED/ldflags the workflow uses, and the assembled zip's contents match. README.md omitted (copied only if present) since it doesn't exist in this repo yet. --- _Imported from beads `archie-core-8cda.4.7.1` · GitHub #777 · type task · priority P2 · created 2026-09-07 · closed 2026-09-07_
sam added the mediumtask labels 2026-10-27 13:39:13 +00:00
sam self-assigned this 2026-10-27 13:39:13 +00:00
sam closed this issue 2026-10-27 13:39:13 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1148