Release 2.1.62 (2026-06-23)

Bug fixes

• retry transient GitHub HTTP 401 Bad credentials errors (#1821) GitHub's API — notably the GraphQL endpoint behind gh pr checks --watch — intermittently returns HTTP 401 "Bad credentials" for a valid token, with the immediately following call succeeding. This burned a release merge step.

Retries are centralized in retry.is_retryable(); every GitHub call path (both pr-checks-watch runners, the JSON check-query calls, and the vrg-gh CLI wrapper) funnels through it. Adding http 401 and bad credentials to _RETRYABLE_PATTERNS covers all of them in one place.

Retrying a 401 is safe even for write operations: a 401 is rejected at authentication, before any mutation occurs.