zeekay b5cb8db1fb docs: a 5xx is not a refusal either, and the wait should grow ...

hanzoai/ci took the same fix further and both corrections apply here. A 429 or a
5xx is the gateway or the throttle answering about ITSELF, not KMS answering
about the secret — treated as final, either one fails a release for a reason
that would be gone a second later. Only a real verdict (2xx, or a 4xx that is
not 429) ends the loop now.

The wait grows 0/5/15/45 rather than three flat threes, because the socket drop
this exists for comes in bursts and a fixed retry lands inside the same one.

The `|| code=000` placement carries a comment now. It belongs on the assignment,
never inside the substitution: `-w` already prints 000 when curl fails, so a
second one makes the variable "000000" — which matches no case, and silently
turns an outage into a refusal that never retries. That is the bug ci found in
its copy; this copy never had it, and the note is what keeps it that way.

2026-08-24 08:55:12 -07:00

..

actions/kms

drop the repeated word, and say what the files do

2026-08-14 15:59:26 -07:00

workflows

docs: a 5xx is not a refusal either, and the wait should grow

2026-08-24 08:55:12 -07:00