[STAGED] chore(ghcr): repoint pull path to nimblecoorg — merge at transfer, do not merge yet#173
Merged
juniperbevensee merged 1 commit intoJul 22, 2026
Conversation
All merge gates satisfied: repo transferred to NimbleCoOrg, owner-derived publisher (#102) shipped the first nimblecoorg image, and the package is now PUBLIC (anon pull verified HTTP 200). Old nimblecoai package stays frozen as the grace window — never delete. Regenerated on post-A-track main (the original branch predated #172's merge and conflicted). Mechanical: 17 files, image path only; camofox + bare hermes-agent untouched. 766/766, tsc clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
juniperbevensee
force-pushed
the
dev/juniperbevensee/ghcr-repoint-nimblecoorg
branch
from
July 22, 2026 04:08
e8d28b6 to
69dfe89
Compare
juniperbevensee
marked this pull request as ready for review
July 22, 2026 04:08
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
1 participant
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.
The HSM pull-path half of the GHCR repoint for the NimbleCoAI→NimbleCoOrg transfer. Pairs with agent-mt #102 (the owner-derived publisher).
What
Flips
ghcr.io/nimblecoai/hermes-agent-mt→ghcr.io/nimblecoorg/hermes-agent-mtacross HSM:DEFAULT_IMAGE_REPO(harness.ts), the compose/config/deploy fallback defaults, UI copy, registry doc-comments, docs pull commands, and the tests that pin the path.camofoxand the barehermes-agentname are left untouched (separate images, not transferring). 727/727, tsc clean.Pre-transfer,
ghcr.io/nimblecoorg/hermes-agent-mthas no image, so merging this early would make new deploys pull a nonexistent image. Merge order:hermes-agent-mt→ NimbleCoOrg.ghcr.io/nimblecoorg/....Deployed instances can flip immediately at launch via
settings.defaultImage(no code merge needed) — this PR is for the baked-in defaults. Keep the oldghcr.io/nimblecoaipackage (frozen) as a pull grace window; never delete it.Why the runbook's plan changed
The runbook assumed CI auto-derived the image path and would silently republish on transfer. It didn't — the publisher hardcoded
nimblecoai(fixed in #102 to be owner-derived). So the corrected sequence is: #102 makes publishing transfer-safe; this PR makes pulling match.🤖 Generated with Claude Code