chore: move sdks to unkeyed/sdks

[chronark]

What does this PR do?

Fixes # (issue)

If there is not an issue for this, please create one first. This is used to tracking purposes and also helps use understand why this PR exists

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

• Chores
  • Removed all files and documentation for the @unkey/api, @unkey/hono, and @unkey/nextjs packages, including source code, tests, configuration, and metadata.
  • Updated dependency version for @unkey/api in the API app to a fixed version.
  • Cleaned up type annotations in API tests for error responses.
• Bug Fixes
  • Adjusted test type annotations to use inline error response types instead of removed shared types.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ac6a4a4

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

[coderabbitai]

📝 Walkthrough

Walkthrough

This change removes the entire source code, tests, configuration, and documentation for the @unkey/api, @unkey/hono, and @unkey/nextjs packages. It also updates a dependency version in apps/api/package.json and refactors several test files in apps/api to eliminate references to the deleted API package.

Changes

Cohort / File(s)	Change Summary
API Package Removal packages/api/*	Entire @unkey/api package deleted, including all source files (src/), tests, configuration (tsconfig.json, tsup.config.js), documentation (README.md, CHANGELOG.md, LICENSE.md), and package.json.
Hono Package Removal packages/hono/*	Entire @unkey/hono package deleted, including source code, tests, configuration, documentation, and package.json.
Next.js Package Removal packages/nextjs/*	Entire @unkey/nextjs package deleted, including source code, configuration, documentation, and package.json.
SDK Integration Test Deletions apps/api/src/integration/sdk/*	All SDK integration tests deleted: create_and_verify.test.ts, create_key_then_update_identity.test.ts, create_key_with_permissions.ts, verify.test.ts, verify_with_ratelimit.test.ts.
Test Type Refactors apps/api/src/integration/verify_permissions.test.ts, apps/api/src/routes/v1_keys_createKey.security.test.ts, apps/api/src/routes/v1_keys_verifyKey.multilimit.test.ts, apps/api/src/routes/v1_migrations_createKey.happy.test.ts	Replaced usage of the ErrorResponse type (previously imported from @unkey/api) with inline type definitions for error response objects in tests. Imports from the deleted package were removed.
Dependency Version Update apps/api/package.json	Changed @unkey/api devDependency from "workspace:^" to "2.0.0".

Sequence Diagram(s)

No sequence diagram generated as the changes are primarily package and test removals, with no new or modified control flow introduced.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~40 minutes

Possibly related PRs

• fix: withUnkey should not fail build (@unkey/nextjs) #2651: Also modifies the withUnkey function and NextContext type in packages/nextjs/src/index.ts, which is deleted in this PR.
• feat: added README.md in /packages/api #2153: Adds a new README.md to packages/api, which is deleted in this PR.
• feat: add all options to verifyKey #2827: Modifies the verifyKey function in packages/api/src/verify.ts, which is deleted in this PR.

Suggested reviewers

• mcstepp
• MichaelUnkey
• perkinsjr

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d0c2bb5 and ac6a4a4.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (38)

• apps/api/package.json (1 hunks)
• apps/api/src/integration/sdk/create_and_verify.test.ts (0 hunks)
• apps/api/src/integration/sdk/create_key_then_update_identity.test.ts (0 hunks)
• apps/api/src/integration/sdk/create_key_with_permissions.ts (0 hunks)
• apps/api/src/integration/sdk/verify.test.ts (0 hunks)
• apps/api/src/integration/sdk/verify_with_ratelimit.test.ts (0 hunks)
• apps/api/src/integration/verify_permissions.test.ts (1 hunks)
• apps/api/src/routes/v1_keys_createKey.security.test.ts (3 hunks)
• apps/api/src/routes/v1_keys_verifyKey.multilimit.test.ts (1 hunks)
• apps/api/src/routes/v1_migrations_createKey.happy.test.ts (1 hunks)
• packages/api/CHANGELOG.md (0 hunks)
• packages/api/LICENSE.md (0 hunks)
• packages/api/README.md (0 hunks)
• packages/api/package.json (0 hunks)
• packages/api/src/client.test.ts (0 hunks)
• packages/api/src/client.ts (0 hunks)
• packages/api/src/errors.ts (0 hunks)
• packages/api/src/index.ts (0 hunks)
• packages/api/src/telemetry.ts (0 hunks)
• packages/api/src/verify.ts (0 hunks)
• packages/api/tsconfig.json (0 hunks)
• packages/api/tsup.config.js (0 hunks)
• packages/hono/CHANGELOG.md (0 hunks)
• packages/hono/LICENSE.md (0 hunks)
• packages/hono/README.md (0 hunks)
• packages/hono/package.json (0 hunks)
• packages/hono/src/index.test.ts (0 hunks)
• packages/hono/src/index.ts (0 hunks)
• packages/hono/tsconfig.json (0 hunks)
• packages/hono/tsup.config.js (0 hunks)
• packages/hono/vitest.config.ts (0 hunks)
• packages/nextjs/CHANGELOG.md (0 hunks)
• packages/nextjs/LICENSE.md (0 hunks)
• packages/nextjs/README.md (0 hunks)
• packages/nextjs/package.json (0 hunks)
• packages/nextjs/src/index.ts (0 hunks)
• packages/nextjs/tsconfig.json (0 hunks)
• packages/nextjs/tsup.config.js (0 hunks)

💤 Files with no reviewable changes (33)

• packages/nextjs/LICENSE.md
• packages/api/LICENSE.md
• packages/hono/LICENSE.md
• packages/api/README.md
• apps/api/src/integration/sdk/create_and_verify.test.ts
• packages/api/src/errors.ts
• packages/api/tsup.config.js
• packages/hono/tsconfig.json
• packages/hono/tsup.config.js
• packages/nextjs/README.md
• packages/hono/vitest.config.ts
• packages/hono/README.md
• packages/hono/package.json
• apps/api/src/integration/sdk/create_key_with_permissions.ts
• packages/nextjs/tsup.config.js
• packages/api/tsconfig.json
• packages/api/src/index.ts
• packages/nextjs/package.json
• apps/api/src/integration/sdk/verify_with_ratelimit.test.ts
• packages/hono/CHANGELOG.md
• packages/api/package.json
• packages/api/src/verify.ts
• packages/hono/src/index.ts
• packages/nextjs/tsconfig.json
• packages/api/src/client.test.ts
• apps/api/src/integration/sdk/create_key_then_update_identity.test.ts
• packages/api/src/telemetry.ts
• packages/api/CHANGELOG.md
• packages/nextjs/CHANGELOG.md
• packages/hono/src/index.test.ts
• apps/api/src/integration/sdk/verify.test.ts
• packages/api/src/client.ts
• packages/nextjs/src/index.ts

🧰 Additional context used

🧠 Learnings (6)

📓 Common learnings

Learnt from: chronark
PR: unkeyed/unkey#2693
File: apps/api/src/routes/v1_keys_updateKey.ts:350-368
Timestamp: 2024-11-29T15:15:47.308Z
Learning: In `apps/api/src/routes/v1_keys_updateKey.ts`, the code intentionally handles `externalId` and `ownerId` separately for clarity. The `ownerId` field will be removed in the future, simplifying the code.

apps/api/package.json (1)

Learnt from: Flo4604
PR: #3421
File: go/apps/api/openapi/openapi.yaml:196-200
Timestamp: 2025-07-03T05:58:10.699Z
Learning: In the Unkey codebase, OpenAPI 3.1 is used, which allows sibling keys (such as description) alongside $ref in schema objects. Do not flag this as an error in future reviews.

apps/api/src/routes/v1_keys_createKey.security.test.ts (5)

Learnt from: chronark
PR: #2693
File: apps/api/src/routes/v1_keys_updateKey.ts:350-368
Timestamp: 2024-11-29T15:15:47.308Z
Learning: In apps/api/src/routes/v1_keys_updateKey.ts, the code intentionally handles externalId and ownerId separately for clarity. The ownerId field will be removed in the future, simplifying the code.

Learnt from: MichaelUnkey
PR: #2114
File: apps/api/src/routes/v1_keys_updateKey.error.test.ts:0-0
Timestamp: 2024-09-27T15:20:05.475Z
Learning: In the v1/keys.updateKey endpoint, the server validates the refill configuration before checking if the key exists. Therefore, tests can assert validation errors without needing to create the key first.

Learnt from: chronark
PR: #2126
File: apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts:36-36
Timestamp: 2024-11-13T19:06:36.786Z
Learning: In the rate limit test files (e.g., apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts), URL parameters like namespaceId and identifier do not need to be URL-encoded in the test code because the values used are always considered safe within the test environment.

Learnt from: mcstepp
PR: #3662
File: apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts:110-147
Timestamp: 2025-07-25T19:11:00.208Z
Learning: In apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts, the user mcstepp prefers to keep mock data fallbacks in POC/demonstration code for simplicity, even if it wouldn't be production-ready. This aligns with the PR being work-in-progress for demonstration purposes.

Learnt from: ogzhanolguncu
PR: #3292
File: apps/dashboard/lib/trpc/routers/key/create.ts:11-14
Timestamp: 2025-06-02T11:09:58.791Z
Learning: In the unkey codebase, TypeScript and the env() function implementation already provide sufficient validation for environment variables, so additional runtime error handling for missing env vars is not needed.

apps/api/src/integration/verify_permissions.test.ts (5)

Learnt from: chronark
PR: #2126
File: apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts:36-36
Timestamp: 2024-11-13T19:06:36.786Z
Learning: In the rate limit test files (e.g., apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts), URL parameters like namespaceId and identifier do not need to be URL-encoded in the test code because the values used are always considered safe within the test environment.

Learnt from: chronark
PR: #3617
File: go/apps/api/openapi/openapi.yaml:3309-3312
Timestamp: 2025-07-16T17:51:57.297Z
Learning: In the Unkey API OpenAPI schema, the permissions query regex for the verifyKey endpoint intentionally allows all whitespace characters (including tabs and newlines) via \s. Do not flag this as an error in future reviews.

Learnt from: chronark
PR: #2544
File: apps/api/src/pkg/env.ts:4-6
Timestamp: 2024-10-23T12:05:31.121Z
Learning: The cloudflareRatelimiter type definition in apps/api/src/pkg/env.ts should not have its interface changed; it should keep the limit method returning Promise<{ success: boolean }> without additional error properties.

Learnt from: mcstepp
PR: #3662
File: apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts:110-147
Timestamp: 2025-07-25T19:11:00.208Z
Learning: In apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts, the user mcstepp prefers to keep mock data fallbacks in POC/demonstration code for simplicity, even if it wouldn't be production-ready. This aligns with the PR being work-in-progress for demonstration purposes.

Learnt from: MichaelUnkey
PR: #2114
File: apps/api/src/routes/v1_keys_updateKey.error.test.ts:0-0
Timestamp: 2024-09-27T15:20:05.475Z
Learning: In the v1/keys.updateKey endpoint, the server validates the refill configuration before checking if the key exists. Therefore, tests can assert validation errors without needing to create the key first.

apps/api/src/routes/v1_keys_verifyKey.multilimit.test.ts (8)

Learnt from: chronark
PR: #2544
File: apps/api/src/pkg/env.ts:4-6
Timestamp: 2024-10-23T12:05:31.121Z
Learning: The cloudflareRatelimiter type definition in apps/api/src/pkg/env.ts should not have its interface changed; it should keep the limit method returning Promise<{ success: boolean }> without additional error properties.

Learnt from: chronark
PR: #2126
File: apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts:36-36
Timestamp: 2024-11-13T19:06:36.786Z
Learning: In the rate limit test files (e.g., apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts), URL parameters like namespaceId and identifier do not need to be URL-encoded in the test code because the values used are always considered safe within the test environment.

Learnt from: chronark
PR: #2294
File: apps/api/src/pkg/keys/service.ts:268-271
Timestamp: 2024-10-20T07:05:55.471Z
Learning: In apps/api/src/pkg/keys/service.ts, ratelimitAsync is a table relation, not a column selection. When querying, ensure that table relations are included appropriately, not as columns.

Learnt from: chronark
PR: #2693
File: apps/api/src/routes/v1_keys_updateKey.ts:350-368
Timestamp: 2024-11-29T15:15:47.308Z
Learning: In apps/api/src/routes/v1_keys_updateKey.ts, the code intentionally handles externalId and ownerId separately for clarity. The ownerId field will be removed in the future, simplifying the code.

Learnt from: MichaelUnkey
PR: #2114
File: apps/api/src/routes/v1_keys_updateKey.error.test.ts:0-0
Timestamp: 2024-09-27T15:20:05.475Z
Learning: In the v1/keys.updateKey endpoint, the server validates the refill configuration before checking if the key exists. Therefore, tests can assert validation errors without needing to create the key first.

Learnt from: mcstepp
PR: #3662
File: apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts:110-147
Timestamp: 2025-07-25T19:11:00.208Z
Learning: In apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts, the user mcstepp prefers to keep mock data fallbacks in POC/demonstration code for simplicity, even if it wouldn't be production-ready. This aligns with the PR being work-in-progress for demonstration purposes.

Learnt from: ogzhanolguncu
PR: #3292
File: apps/dashboard/lib/trpc/routers/key/create.ts:11-14
Timestamp: 2025-06-02T11:09:58.791Z
Learning: In the unkey codebase, TypeScript and the env() function implementation already provide sufficient validation for environment variables, so additional runtime error handling for missing env vars is not needed.

Learnt from: Flo4604
PR: #3421
File: go/apps/api/openapi/openapi.yaml:196-200
Timestamp: 2025-07-03T05:58:10.699Z
Learning: In the Unkey codebase, OpenAPI 3.1 is used, which allows sibling keys (such as description) alongside $ref in schema objects. Do not flag this as an error in future reviews.

apps/api/src/routes/v1_migrations_createKey.happy.test.ts (5)

Learnt from: chronark
PR: #2693
File: apps/api/src/routes/v1_keys_updateKey.ts:350-368
Timestamp: 2024-11-29T15:15:47.308Z
Learning: In apps/api/src/routes/v1_keys_updateKey.ts, the code intentionally handles externalId and ownerId separately for clarity. The ownerId field will be removed in the future, simplifying the code.

Learnt from: mcstepp
PR: #3662
File: apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts:110-147
Timestamp: 2025-07-25T19:11:00.208Z
Learning: In apps/dashboard/lib/trpc/routers/deployment/getOpenApiDiff.ts, the user mcstepp prefers to keep mock data fallbacks in POC/demonstration code for simplicity, even if it wouldn't be production-ready. This aligns with the PR being work-in-progress for demonstration purposes.

Learnt from: chronark
PR: #2126
File: apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts:36-36
Timestamp: 2024-11-13T19:06:36.786Z
Learning: In the rate limit test files (e.g., apps/api/src/routes/v1_ratelimit_getOverride.happy.test.ts), URL parameters like namespaceId and identifier do not need to be URL-encoded in the test code because the values used are always considered safe within the test environment.

Learnt from: chronark
PR: #2544
File: apps/api/src/pkg/env.ts:4-6
Timestamp: 2024-10-23T12:05:31.121Z
Learning: The cloudflareRatelimiter type definition in apps/api/src/pkg/env.ts should not have its interface changed; it should keep the limit method returning Promise<{ success: boolean }> without additional error properties.

Learnt from: MichaelUnkey
PR: #2114
File: apps/api/src/routes/v1_keys_updateKey.error.test.ts:0-0
Timestamp: 2024-09-27T15:20:05.475Z
Learning: In the v1/keys.updateKey endpoint, the server validates the refill configuration before checking if the key exists. Therefore, tests can assert validation errors without needing to create the key first.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Test API / API Test Local
• GitHub Check: Build / Build
• GitHub Check: Test Packages / Test

🔇 Additional comments (5)

apps/api/package.json (1)

16-16: Confirmed availability of @unkey/api@2.0.0

The npm registry shows that version 2.0.0 is published and available, so updating the dependency to use this fixed version is correct.

apps/api/src/integration/verify_permissions.test.ts (1)

201-201: LGTM - Clean refactor to inline error type.

The replacement of ErrorResponse with the inline type { error: { code: string } } is consistent with the removal of the @unkey/api package. The change maintains the same type structure and test functionality.

apps/api/src/routes/v1_migrations_createKey.happy.test.ts (1)

484-486: LGTM - Consistent inline error type replacement.

The multi-line inline type definition { error: { code: string } } properly replaces the imported ErrorResponse type while maintaining the same structure for test assertions.

apps/api/src/routes/v1_keys_createKey.security.test.ts (1)

96-96: LGTM - Consistent error type refactoring across permission tests.

All three instances correctly replace ErrorResponse with the inline type { error: { code: string } }. The changes maintain test functionality while removing dependency on the removed @unkey/api package.

Also applies to: 124-124, 152-152

apps/api/src/routes/v1_keys_verifyKey.multilimit.test.ts (1)

112-112: LGTM - Final consistent application of inline error type.

The replacement of ErrorResponse with { error: { code: string } } completes the consistent refactoring pattern across all affected test files, maintaining functionality while removing the dependency on the removed package.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 07-31-chore_move_sdks_to_unkeyed_sdks

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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 generate unit tests to generate unit tests for 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.

[vercel]

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	Jul 31, 2025 10:22am
engineering	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 31, 2025 10:22am

[chronark]

• chore: move sdks to unkeyed/sdks #3701 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

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

[graphite-app]

[graphite-app]

Graphite Automations

"Post a GIF when PR approved" took an action on this PR • (07/31/25)

1 gif was posted to this PR based on Andreas Thomas's automation.