fix(release): publish runtime under repository owner#68
Merged
Conversation
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.
Summary
The MLClaw repository moved to the Hugging Face organization, but its release workflow still tried to push runtime images into Onur's personal GHCR namespace.
GitHub correctly rejected that cross-owner write after spending time building both architectures.
This change moves the runtime image to
ghcr.io/huggingface/mlclawand prepares patch release 0.4.5.What Changed
Runtime images now live under the same owner as the source repository and release workflow.
The CLI, Dockerfile, user documentation, archived plans, tests, and release automation all use the same image name.
ghcr.io/huggingface/mlclaw.huggingface/mlclaw.Testing
The application and website quality gates are green locally.
The application suite covers runtime image generation and package contents.
npm run build && npm run check(317 tests, 97.92% statement coverage, build, package, secret, DRY, and Slophammer gates)npm --prefix website ci && npm --prefix website run check(2 tests, 100% coverage, static build, DRY gate)Risks
Existing deployments keep using their explicitly stored old image until updated.
New and updated deployments use the new Hugging Face-owned image after 0.4.5 is published.
The old package name is not retained as a fallback.