Skip to content

ci(images): publish amd64 and arm64 images to GHCR for each release - #557

Merged
adeelahmad merged 1 commit into
mainfrom
claude/project-thread-o74dm3
Oct 18, 2026
Merged

adeelahmad merged 1 commit into
mainfrom
claude/project-thread-o74dm3

Conversation

@adeelahmad

Copy link
Copy Markdown
Owner

Requested by Adeel · project thread

Description

Before: every install builds Lens's images on the machine itself, which on a Raspberry Pi takes a long time; no release ships images.

After: each release publishes Lens's own images to GHCR, built for amd64 and arm64:

  • ghcr.io/adeelahmad/lens-backend:X.Y.Z-full (also X.Y.Z, latest-full, latest)
  • ghcr.io/adeelahmad/lens-backend:X.Y.Z-lean (also latest-lean)
  • ghcr.io/adeelahmad/lens-frontend:X.Y.Z (also latest)

How: a new images.yml builds each image on a runner of its architecture (GitHub's ubuntu-24.04-arm for arm64, no emulation), pushes by digest, then joins the two digests into one multi-arch tag and checks both platforms are in it. release.yml starts it for the tag like the other package workflows; it can also be run by hand with a tag to publish an existing release. latest moves only for the newest release. Only the built-in GITHUB_TOKEN is used; no new service. A PR that changes images.yml builds all six without pushing (this PR does).

The install line doesn't use the images yet: an opt-in to pull them comes in the next PR, and the default stays build-from-source until the owner decides.

Motivation and Context

Queued item "prebuilt multi-arch images", started by the owner's "Start all".

Types of changes

  • New feature (non-breaking change which adds functionality)

Checklist:

  • The title is a Conventional Commit.
  • My code follows the code style of this project (make hooks checks it on commit).
  • I added or updated tests. (the workflow's own checks: Both architectures are there; requirement row in docs/requirements.md)
  • My change requires documentation updates, and I have updated docs/ accordingly. (docs/deployment.md#prebuilt-images)
  • Users need more than the title to understand it: n/a.

Done questions (AGENTS.md)

  • Goal: images on each release; merged on green.
  • Agents: n/a, CI only; the install opt-in follows.
  • Zero setup: nothing to do on installs; nothing changes for them.
  • Fewest clicks: n/a.
  • Configurable: n/a, no setting.
  • Light: arm64 images are what lets a Pi skip building (next PR).
  • Private and secure: built in CI from the tag with GITHUB_TOKEN; installs don't pull yet, so the threat model changes in the opt-in PR.
  • Cost: GitHub's free runners and registry for a public repo; no paid service.
  • User decides: no default changes.
  • Upgrades: n/a for stored data; nothing changes for installs.
  • Honest: README says only that releases publish the images.
  • Tests, docs and generated files updated.
  • Open standards: OCI images; no new dependencies.
  • Reported with evidence. Refine later: images for the opt-in profiles (MCP runner, Matterbridge, StyleTTS2), and Synology/QNAP packages reusing these images.
  • Reuse: Docker's build-push/imagetools actions already used in cloudron.yml.

Local CI: ci/local-ci.sh --jobs pre-commit,title passed; actionlint clean.


Generated by Claude Code

@adeelahmad adeelahmad self-assigned this Oct 18, 2026
@adeelahmad
adeelahmad merged commit 0f3e256 into main Oct 18, 2026
16 checks passed
@adeelahmad
adeelahmad deleted the claude/project-thread-o74dm3 branch October 18, 2026 07:29
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.

2 participants