registry: move image and repo references to the Jinemi namespace #150
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Jinemi/thermograph#150
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/registry-namespace-admin-emi"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Repos moved to the
Jinemiorg, but Forgejo does not transfer container packages with a repo, so the two drifted apart:build-push.ymlderives its push path from the repository name, nowjinemi/thermograph— the next backend or frontend build publishes there.emi/thermograph/*, which is not an account at all:emiis auser_redirecttoadmin_emi, left from renaming that account.The next image build would have published somewhere no deploy looks. This points the image paths at
jinemi/thermograph/*, the clone URLs atJinemi/thermograph, and the registry logins atadmin_emi— the account that actually owns the tokens.Registry paths are lowercase because OCI references admit no uppercase, which is why
build-push.ymlalready pipes the derived path throughtr. Clone URLs keep the canonicalJinemi.Unchanged on purpose:
thermograph-infra,thermograph-observabilityand the retired*/apppackages stay underadmin_emi. They did not move.Done out of band before this lands, so the switch has something to pull:
sha-18f50ad09b2e,sha-deb039ee249f, backend + frontend) andci-runner:v1/v2copied into theJineminamespace.Jinemi/thermograph.git; stored docker logins re-issued asadmin_emi.jinemi/thermograph/ci-runner:v2.Repos moved to the Jinemi org; the container packages did not follow, since Forgejo does not transfer packages with a repo. The deploy path still resolved `emi/thermograph/*` — a user_redirect to admin_emi — while build-push.yml derives its push path from ${github.repository}, now jinemi/thermograph. The next backend or frontend build would have published somewhere no deploy looks. Point the image paths at jinemi/thermograph/* (lowercase: OCI references admit no uppercase, which is why build-push.yml already pipes through tr), the clone URLs at Jinemi/thermograph, and the registry logins at admin_emi — the account that actually owns the tokens, rather than the redirect. The live tags and both ci-runner tags were copied into the Jinemi namespace first, so the switch has something to pull. thermograph-infra, thermograph-observability and the retired */app packages stay under admin_emi; they did not move.