Build & push multi-arch images to the Forgejo container registry #3

New issue

Open

opened 2026-07-07 16:51:15 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-07-07 16:51:15 +00:00

Contributor

Goal

Publish authoritative container images to our own registry so there is always a canonical image source (and a foundation for full CD later).

Scope

Push linux/amd64 + linux/arm64 images to the Forgejo container registry:
- git.rhoving.com/rbrooks/iris-wled:<tag>
- git.rhoving.com/rbrooks/iris-wled:latest
Authenticate the workflow to the registry using the Forgejo Actions token (docker/login-action against git.rhoving.com).
Stop publishing to GHCR (see the release-automation issue for the tag-triggered path).

Acceptance criteria

Images for both architectures land in the Forgejo registry
latest and the version tag are both pushed
Registry auth uses the built-in Actions token, no long-lived PAT

Depends on: CI migration to Forgejo Actions.

## Goal Publish authoritative container images to our own registry so there is always a canonical image source (and a foundation for full CD later). ## Scope - Push `linux/amd64` + `linux/arm64` images to the Forgejo container registry: - `git.rhoving.com/rbrooks/iris-wled:<tag>` - `git.rhoving.com/rbrooks/iris-wled:latest` - Authenticate the workflow to the registry using the Forgejo Actions token (`docker/login-action` against `git.rhoving.com`). - Stop publishing to GHCR (see the release-automation issue for the tag-triggered path). ## Acceptance criteria - [ ] Images for both architectures land in the Forgejo registry - [ ] `latest` and the version tag are both pushed - [ ] Registry auth uses the built-in Actions token, no long-lived PAT Depends on: CI migration to Forgejo Actions.

claude-bot added the

labels

2026-07-07 16:53:24 +00:00

claude-bot referenced this issue

2026-07-07 16:59:04 +00:00

Move CI/CD to Forgejo Actions; add CHANGELOG; issues-driven roadmap #19