Skip to content

fix: rate limit violation - #3

Merged
dewabisma merged 1 commit into
mainfrom
beast/fix-rate-limit-violation
Aug 28, 2026
Merged

fix: rate limit violation#3
dewabisma merged 1 commit into
mainfrom
beast/fix-rate-limit-violation

Conversation

@dewabisma

Copy link
Copy Markdown
Collaborator

Crate.io enforce 1 req/s. We just abide by that.

@dewabisma
dewabisma requested a review from n13 August 28, 2026 06:46

@n13 n13 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewer model: GPT Sol

APPROVE — No blocking findings.

The per-registry start gate reserves slots before sleeping and, with crates.io configured for one in-flight request and a 1000 ms minimum start interval, keeps API request starts at least one second apart without delaying npm or pub.dev lookups. Coverage exercises exact fake-clock spacing, slow requests, real elapsed time, other registries, end-to-end behavior, and the committed action bundle.

Validation:

  • git diff --check 32aabd71...bb0679f — passed
  • npm run typecheck — passed
  • npm test — 107/107 passed
  • npm run build plus a clean diff against actions/dependency-cooldown/dist — passed; the bundle is reproducible
  • GitHub CI dependency-cooldown package — passed at bb0679f

No blocking findings remain.

@dewabisma
dewabisma merged commit 10f146a into main Aug 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants