ScreenTinker afe3f7f57f Retry the ghcr push once — a transient 403 should not cost a release ... ghcr refused the 1.9.29 push with "denied: permission_denied: Error from intermediary with HTTP status code 403", then accepted the identical build on a manual re-run minutes later. Nothing about the token, the permissions or the workflow changed in between; the registry simply said no once. The timing is what makes it worth handling. The GitHub Release job has already published by the time this runs, so a failure here leaves a tag that exists with no image behind it — alpha and every self-hoster pulling :latest see a version that is announced and unpullable, which reads as a broken release rather than a hiccup at a registry. It also needs a human to notice and re-run, which is the part that does not scale. One retry, after a pause, and a second refusal still fails the release. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Uaeo9MvzKoyXuN6ZsbhtkL		2026-08-06 09:10:17 -05:00
..
workflows	Retry the ghcr push once — a transient 403 should not cost a release	2026-08-06 09:10:17 -05:00