ci(ghcr): derive publish namespace from repository_owner (transfer-safe)#102
Merged
Merged
Conversation
The fork's GHCR publisher hardcoded ghcr.io/nimblecoai/... — so a transfer to NimbleCoOrg would leave CI trying to push to a namespace it no longer owns (permission-denied failure, not a silent republish as the runbook assumed). Derive the namespace from github.repository_owner (docker/metadata-action lowercases it). Behavior is IDENTICAL today (owner NimbleCoAI -> nimblecoai) and auto-repoints to nimblecoorg the instant the repo transfers — no coordinated code change, no launch-window timing. Also drops the deprecated .../hermes-agent dual-publish alias (removal date 2026-07-15, now passed). Safe to merge anytime: pre-transfer this publishes exactly where it does now. Touches .github/ -> needs the ci-reviewed label gate. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ CI-sensitive file review passedThe |
NimbleCoAI
added
the
ci-reviewed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Makes the fork's GHCR publisher transfer-safe ahead of the NimbleCoAI→NimbleCoOrg move.
Why
ghcr-publish.ymlhardcodedghcr.io/nimblecoai/hermes-agent-mt. Correction to the transfer runbook: it assumed CI derives the path fromgithub.repositoryand would silently republish to a new namespace on transfer. It doesn't — the path is hardcoded, so post-transfer CI would try to push to thenimblecoainamespace NimbleCoOrg no longer owns and fail (permission denied), not silently.Fix
Derive the namespace from
github.repository_owner(docker/metadata-actionlowercases it):ghcr.io/nimblecoai/hermes-agent-mt).nimblecoorgthe instant the repo transfers — no coordinated timing, no launch-window code change..../hermes-agentdual-publish alias (removal date 2026-07-15, now passed).Safe to merge anytime
Pre-transfer this publishes exactly where it does now, so it can land ahead of the move to de-risk it. The old-owner GHCR package is retained (frozen) as a pull grace window — never delete it.
Notes
.github/→ needs theci-reviewedlabel gate (same as chore: sync with upstream 2026-07-18 (resolve stuck #74/#82 conflicts) #94). The change only narrows/parameterizes the image path; no permission or trigger changes.🤖 Generated with Claude Code