Skip to content

feat: update ratelimit sdk to v2 #3236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 8, 2025
Merged

feat: update ratelimit sdk to v2 #3236

merged 1 commit into from
May 8, 2025

Conversation

chronark
Copy link
Collaborator

@chronark chronark commented May 8, 2025

Update the latest version and update docs to reflect the API changes.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How should this be tested?

  • Test A
  • Test B

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read Contributing Guide
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand areas
  • Ran pnpm build
  • Ran pnpm fmt
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Unkey Docs if changes were necessary

Summary by CodeRabbit

  • Documentation

    • Updated API documentation to remove references to the deprecated async parameter and related descriptions from all relevant sections.
    • Improved formatting and consistency in code examples and response schemas.
    • Updated GitHub repository links and streamlined usage examples for clarity.
  • Chores

    • Upgraded the @unkey/ratelimit dependency to a stable release version in the dashboard application.

Update the latest version and update docs to reflect the API changes.
Copy link

changeset-bot bot commented May 8, 2025

⚠️ No Changeset found

Latest commit: 73fb892

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented May 8, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 8, 2025 11:55am
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 8, 2025 11:55am

Copy link
Contributor

coderabbitai bot commented May 8, 2025

📝 Walkthrough

Walkthrough

The changes update the @unkey/ratelimit dependency in the dashboard to a stable version and revise the documentation for ratelimit override APIs. All references to the async parameter are removed from the documentation, and example code and formatting are updated for consistency. No code or API signatures are altered.

Changes

File(s) Change Summary
apps/dashboard/package.json Updated @unkey/ratelimit dependency from canary pre-release to stable version.
apps/docs/libraries/ts/ratelimit/override/get-override.mdx
apps/docs/libraries/ts/ratelimit/override/list-overrides.mdx
apps/docs/libraries/ts/ratelimit/override/set-override.mdx
apps/docs/libraries/ts/ratelimit/override/overview.mdx
Removed documentation of the async parameter from override API docs; adjusted formatting and whitespace.
apps/docs/libraries/ts/ratelimit/ratelimit.mdx Removed TLDR example, updated GitHub link, and omitted async, meta, and resources from parameter docs.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Docs
    participant Ratelimit API

    User->>Docs: Reads ratelimit override API documentation
    Docs-->>User: Presents updated docs (no `async` parameter)
    User->>Ratelimit API: Uses override APIs as documented
    Ratelimit API-->>User: Returns responses (no reference to `async`)
Loading

Possibly related PRs

Suggested labels

Documentation, 🕹️ oss.gg, :joystick: 150 points

Suggested reviewers

  • perkinsjr
  • mcstepp
  • MichaelUnkey
  • ogzhanolguncu

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

github-actions bot commented May 8, 2025

Thank you for following the naming conventions for pull request titles! 🙏

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (5)
apps/docs/libraries/ts/ratelimit/override/set-override.mdx (2)

7-7: Clean up extraneous blank lines.
There are several inserted/removed blank lines around the request and response examples. Removing or standardizing these will improve readability and consistency across the docs.

Also applies to: 53-53, 68-68, 70-70


57-59: Standardize indentation in the second code example.
The parameter lines in the second setOverride snippet have shifted indentation. Align them to your style guide (e.g., 2 or 4 spaces) to maintain consistency.

apps/docs/libraries/ts/ratelimit/override/list-overrides.mdx (1)

61-61: Remove unintended blank/trailing whitespace around examples.
Several blank lines and trailing whitespace markers have appeared before and after the listOverrides code blocks. Cleaning these up will keep the layout consistent with other examples.

Also applies to: 67-67, 70-70, 93-93

apps/docs/libraries/ts/ratelimit/override/get-override.mdx (2)

52-52: Align code snippet formatting.
The object key lines (identifier, namespaceId) have inconsistent spacing and indentation. Ensure there’s a space after the colon and uniform indent (e.g., 2 spaces) for better readability.

Also applies to: 59-60


56-56: Remove extra blank lines around the code blocks.
There are stray blank lines before and after the example snippets. Trimming these will keep the examples visually compact and consistent.

Also applies to: 77-77

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 78ed03a and 73fb892.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (6)
  • apps/dashboard/package.json (1 hunks)
  • apps/docs/libraries/ts/ratelimit/override/get-override.mdx (2 hunks)
  • apps/docs/libraries/ts/ratelimit/override/list-overrides.mdx (2 hunks)
  • apps/docs/libraries/ts/ratelimit/override/overview.mdx (0 hunks)
  • apps/docs/libraries/ts/ratelimit/override/set-override.mdx (3 hunks)
  • apps/docs/libraries/ts/ratelimit/ratelimit.mdx (1 hunks)
💤 Files with no reviewable changes (1)
  • apps/docs/libraries/ts/ratelimit/override/overview.mdx
⏰ Context from checks skipped due to timeout of 90000ms (25)
  • GitHub Check: Test Go API Local / Test (Shard 8/8)
  • GitHub Check: Test Go API Local / Test (Shard 6/8)
  • GitHub Check: Test Go API Local / Test (Shard 1/8)
  • GitHub Check: Test Go API Local / Test (Shard 7/8)
  • GitHub Check: Test Go API Local / Test (Shard 5/8)
  • GitHub Check: Test Go API Local / Test (Shard 3/8)
  • GitHub Check: Test Go API Local / Test (Shard 2/8)
  • GitHub Check: Test Go API Local / Test (Shard 4/8)
  • GitHub Check: Build / Build
  • GitHub Check: Test API / API Test Local
  • GitHub Check: Test Packages / Test ./packages/rbac
  • GitHub Check: Test Packages / Test ./apps/dashboard
  • GitHub Check: Test Packages / Test ./internal/clickhouse
  • GitHub Check: Test Packages / Test ./packages/nextjs
  • GitHub Check: Test Packages / Test ./internal/resend
  • GitHub Check: Test Packages / Test ./packages/api
  • GitHub Check: Test Packages / Test ./packages/cache
  • GitHub Check: Test Packages / Test ./packages/hono
  • GitHub Check: Test Packages / Test ./internal/keys
  • GitHub Check: Test Packages / Test ./internal/hash
  • GitHub Check: Test Packages / Test ./internal/id
  • GitHub Check: Test Packages / Test ./internal/billing
  • GitHub Check: Test Packages / Test ./internal/encryption
  • GitHub Check: autofix
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (2)
apps/dashboard/package.json (1)

55-55: Update dependency to stable @unkey/ratelimit version.
The dependency was updated from the canary pre‐release to the stable ^2.0.0, aligning with the rest of the SDK.
Ensure you run npm install and execute the dashboard’s test suite to catch any compatibility issues with the stable release.

apps/docs/libraries/ts/ratelimit/ratelimit.mdx (1)

10-10: Approve updated GitHub link to ratelimit/ts subdirectory.
The card now points to the TypeScript SDK folder (ratelimit/ts), which is more precise.

const overrides = await unkey.listOverrides({
nameSpaceId:"rlns_12345",
const overrides = await unkey.listOverrides({
nameSpaceId:"rlns_12345",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix property name casing in example.
The example uses nameSpaceId, but the correct parameter key is namespaceId (lowercase “s”). Please update to match the API.

Merged via the queue into main with commit 78ecc51 May 8, 2025
37 of 41 checks passed
@chronark chronark deleted the ratelimit-v2-sdk branch May 8, 2025 11:59
@coderabbitai coderabbitai bot mentioned this pull request Aug 21, 2025
18 tasks
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