chore(localizations): Generate missing API keys locales #6223

wobsoriano · 2025-06-30T17:01:33Z

Description

Checklist

pnpm test runs as expected.
pnpm build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

Summary by CodeRabbit

New Features
- Added placeholders for API key management, billing history, payment statements, and subscription management across all supported languages.
- Expanded localization files with new sections for API keys, payment history tables, statements, and related navigation items in organization and user profile pages.
- Introduced new untranslated keys for form fields and UI labels related to API keys and billing.
Chores
- Added a changeset entry documenting the update for localization placeholders.

changeset-bot · 2025-06-30T17:01:37Z

🦋 Changeset detected

Latest commit: d49bd74

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 4 packages

Name	Type
@clerk/localizations	Patch
@clerk/clerk-js	Patch
@clerk/chrome-extension	Patch
@clerk/clerk-expo	Patch

Not sure what this means? Click here to learn what changesets are.

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

vercel · 2025-06-30T17:01:41Z

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

Name	Status	Preview	Comments	Updated (UTC)
clerk-js-sandbox	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 30, 2025 5:06pm

coderabbitai · 2025-06-30T17:05:30Z

📝 Walkthrough

Walkthrough

This change introduces a new changeset file documenting a patch update for the @clerk/localizations package. The update adds numerous new localization keys across many language resource files, primarily for API key management, billing, payment history, statements, and organization/user profile UI sections. The additions include new nested structures and placeholders for API key actions, form fields, confirmation dialogs, payment tables, subscription lists, and related navigation entries. Most new keys are initialized as undefined placeholders for future translations, with some actual translations provided in specific locales. No existing keys or translations are removed or altered; the changes are purely additive and structural.

Possibly related PRs

feat(localizations): add pt-BR locales for billing elements #6058: Fills in actual Portuguese (Brazil) translations for billing-related keys in the pt-BR localization file, which were introduced as placeholders in this PR.
feat(clerk-js,clerk-react,nextjs): Introduce <APIKeys /> AIO component #5858: Introduces the <APIKeys /> component and its UI/API integration, which is directly supported by the localization keys for API keys management added in this PR.
es-CR localizations #6178: Introduces the initial full Spanish (Costa Rica) localization file, which is extended in this PR with new keys for API keys, billing, and payment history.

Suggested reviewers

tmilewski

🪧 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 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.

coderabbitai

Actionable comments posted: 3

🧹 Nitpick comments (2)

packages/localizations/src/vi-VN.ts (1)

245-251: Track undefined placeholders for future translation work.

The extensive billing and payment history sections have been added consistently across both profile types. While the undefined placeholders are appropriate, consider tracking these for future Vietnamese translation work to ensure complete localization coverage.

Consider adding a comment or tracking mechanism to identify which keys still need Vietnamese translations, as this represents a significant number of UI elements that will display as missing translations until completed.

Also applies to: 270-270, 275-285, 289-291, 893-899, 918-918, 923-933, 937-939

packages/localizations/src/hu-HU.ts (1)

236-238: LGTM: Systematic addition of billing and API key management keys.

The comprehensive additions for billing, payment history, statements, and API key management maintain perfect structural consistency with the Vietnamese file. This systematic approach ensures uniform localization infrastructure across languages.

The Hungarian file follows the same pattern of extensive undefined placeholders. Consider implementing a centralized tracking system for incomplete translations across all locale files to manage the translation workload effectively.

Also applies to: 244-250, 269-269, 274-284, 288-290, 358-358, 877-879, 896-902, 921-921, 926-936, 940-942, 1062-1062

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 01a0f29 and d49bd74.

📒 Files selected for processing (42)

.changeset/eleven-pigs-juggle.md (1 hunks)
packages/localizations/src/ar-SA.ts (12 hunks)
packages/localizations/src/be-BY.ts (12 hunks)
packages/localizations/src/bg-BG.ts (12 hunks)
packages/localizations/src/ca-ES.ts (12 hunks)
packages/localizations/src/cs-CZ.ts (12 hunks)
packages/localizations/src/da-DK.ts (12 hunks)
packages/localizations/src/de-DE.ts (7 hunks)
packages/localizations/src/el-GR.ts (12 hunks)
packages/localizations/src/en-GB.ts (12 hunks)
packages/localizations/src/en-US.ts (7 hunks)
packages/localizations/src/es-CR.ts (15 hunks)
packages/localizations/src/es-ES.ts (12 hunks)
packages/localizations/src/es-MX.ts (12 hunks)
packages/localizations/src/fi-FI.ts (12 hunks)
packages/localizations/src/fr-FR.ts (12 hunks)
packages/localizations/src/he-IL.ts (12 hunks)
packages/localizations/src/hr-HR.ts (12 hunks)
packages/localizations/src/hu-HU.ts (12 hunks)
packages/localizations/src/id-ID.ts (12 hunks)
packages/localizations/src/is-IS.ts (12 hunks)
packages/localizations/src/it-IT.ts (12 hunks)
packages/localizations/src/ja-JP.ts (12 hunks)
packages/localizations/src/ko-KR.ts (12 hunks)
packages/localizations/src/mn-MN.ts (12 hunks)
packages/localizations/src/nb-NO.ts (12 hunks)
packages/localizations/src/nl-BE.ts (12 hunks)
packages/localizations/src/nl-NL.ts (12 hunks)
packages/localizations/src/pl-PL.ts (12 hunks)
packages/localizations/src/pt-BR.ts (12 hunks)
packages/localizations/src/pt-PT.ts (12 hunks)
packages/localizations/src/ro-RO.ts (12 hunks)
packages/localizations/src/ru-RU.ts (12 hunks)
packages/localizations/src/sk-SK.ts (12 hunks)
packages/localizations/src/sr-RS.ts (12 hunks)
packages/localizations/src/sv-SE.ts (12 hunks)
packages/localizations/src/th-TH.ts (12 hunks)
packages/localizations/src/tr-TR.ts (12 hunks)
packages/localizations/src/uk-UA.ts (12 hunks)
packages/localizations/src/vi-VN.ts (12 hunks)
packages/localizations/src/zh-CN.ts (12 hunks)
packages/localizations/src/zh-TW.ts (12 hunks)

🧰 Additional context used

📓 Path-based instructions (6)

`**/*.{js,jsx,ts,tsx}`: All code must pass ESLint checks with the project's conf...

**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Use Prettier for consistent code formatting
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Validate all inputs and sanitize outputs
Implement proper logging with different levels

📄 Source: CodeRabbit Inference Engine (.cursor/rules/development.mdc)