staging #1

Merged

pyaniz merged 2 commits from staging into main

2026-08-14 18:00:21 -05:00

pyaniz commented

2026-08-14 18:00:14 -05:00

Owner

No description provided.

pyaniz added 2 commits

2026-08-14 18:00:14 -05:00

ci: publish to the Forgejo registry, never Docker Hub 2b31bb703b

An unset REGISTRY_HOST variable made both the login step and the image tags
fall back to Docker Hub, so builds were pushed there instead of Forgejo.

Resolve the registry from GITHUB_SERVER_URL when REGISTRY_HOST is not set, so
the workflow targets the Forgejo instance it is running on without depending
on a variable being configured first. Fail the job with an explicit message if
the target still resolves to Docker Hub or to an empty host, rather than
silently publishing to the wrong registry.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

fix: point deploy manifests at the correct registry path 8855fa4884

The Forgejo repository is pyaniz/mtg-bot, so the workflow publishes to
git.liniz.net/pyaniz/mtg-bot. The Helm values and compose file still referred
to mtg-tbot, which would fail to pull.

The Helm release name, namespace, and Secret name are local identifiers and
are left as they are; only the image path has to match the registry.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

pyaniz merged commit 46de11c386 into main

2026-08-14 18:00:21 -05:00

pyaniz referenced this pull request from a commit

2026-08-14 18:00:23 -05:00

Merge pull request 'staging' (#1) from staging into main