77f520823c
All checks were successful
🚀 Deploy / 🧪 Test (pull_request) Successful in 1m30s
🚀 Deploy / ʦ TypeScript (pull_request) Successful in 1m16s
🚀 Deploy / 🔍 Lint (pull_request) Successful in 48s
🚀 Deploy / 🐳 Build (pull_request) Has been skipped
🚀 Deploy / 🚀 Deploy (pull_request) Has been skipped
- Move notifyPickMadeOnDiscord() before checkAndTriggerNextAutodraft() in both executeAutoPick() and the manual pick action. Previously the triggering pick's announcement fired after all chained autodraft picks had already announced, causing Discord to show e.g. pick #106 before #105 before #104. Now each pick announces itself before the next pick in the chain is triggered. - Add a single retry with Retry-After delay in sendDiscordWebhook() on HTTP 429. A burst of consecutive autodraft picks could hit Discord's per-webhook rate limit and silently drop announcements. Use || 1 (not ?? 1) to handle non-numeric/NaN headers, and cap at 10 s so that awaited callers such as the draft-order settings actions are never hung for a full global rate-limit window. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| autodraft.update.ts | ||
| draft.adjust-time-bank.ts | ||
| draft.force-autopick.ts | ||
| draft.force-manual-pick.ts | ||
| draft.make-pick.ts | ||
| draft.pause.ts | ||
| draft.replace-pick.ts | ||
| draft.resume.ts | ||
| draft.rollback.ts | ||
| draft.start.ts | ||
| queue.add.ts | ||
| queue.clear.ts | ||
| queue.remove.ts | ||
| queue.reorder.ts | ||
| seasons.$seasonId.draft.ts | ||
| user.timezone.ts | ||
| watchlist.toggle.ts | ||