Publishing warp_engine hit it: a credentials key written as the host URL
never matches --host, because RubyGems normalizes those keys. gem push
then falls back to signing in against an endpoint Gitea does not have,
and reports "404 page not found" — which points nowhere near the cause.
Also notes that fixing a release pipeline means re-tagging: Woodpecker
reads the config from the tagged commit, so a retry on the old tag would
run the old, broken config.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>