v1.2.0 — ghcr-token for user-owned packages
Found by the first real release, which failed with:
ghcr.io/cshuttle/topology:latest does not exist — nothing to promote.
It existed. The registry returns the same not found for an unauthorised read, and on a personal account a package bootstrapped by a manual push is user-owned — so the repo-scoped GITHUB_TOKEN 403s on it, reads included.
- Optional
ghcr-tokensecret, used for the crane login when supplied. Repos that push with a classic PAT pass the same PAT. Omit it andGITHUB_TOKENis used exactly as before. - The error message no longer asserts absence for what is almost always auth. It prints crane's own message and names both remedies: pass the token, or grant the repo access under the package's Manage Actions access settings and drop the secret.
Minor, not patch: callers gain an input some of them need to set, and nothing breaks for a caller that omits it.