This repository was archived by the owner on Oct 16, 2026. It is now read-only.
Repository navigation
Keep GHCR builds green when visibility is private - #6
Merged
Merged
Conversation
Co-authored-by: Dominic Letz <dominicletz@users.noreply.github.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Investigation
The merged workflow's image push succeeded, but the visibility request failed with curl exit 22. The exact response was:
{ "message": "Not Found", "documentation_url": "https://docs.github.com/rest", "status": "404" }The repository owner is a user (
dominicletz), andpackages: writeis sufficient to publish the image but does not grant the package-admin operation needed to change visibility. GitHub's current documented Packages REST endpoints do not expose a supported visibility-update endpoint for this Actions token.Fix
continue-on-erroragentyardto PublicGHCR_TOKENon the normal deploy path; private-package credentials remain an optional fallbackFirst deploy after merging
Open the package settings at
https://github.com/users/dominicletz/packages/container/agentyard/settings, choose Danger Zone → Change visibility → Public, and confirm the package name before relying on the automatic production deploy. Then bootstrap the server.envfrom.env.prod.exampleand configure the deploy SSH secrets. No GHCR secret is needed once the package is public.Verification
git diff --checkactionlint .github/workflows/*.yml