Skip to content

fix(localizations): Use correct date params in API key dates #6121

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 3 commits into from
Jun 13, 2025

Conversation

wobsoriano
Copy link
Member

@wobsoriano wobsoriano commented Jun 13, 2025

Description

Fixes incorrect locale parameters for API keys last used dates

Before:

Screenshot 2025-06-13 at 2 32 51 PM

After:

Screenshot 2025-06-13 at 2 34 09 PM

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

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Chores

    • Added an empty changeset file for tracking future changes.
  • Style

    • Improved the clarity and accuracy of time interval placeholders in English localization for API key usage messages.
  • Chores

    • Updated bundle size limits for core JavaScript files to accommodate slight increases.

@wobsoriano wobsoriano requested review from aeliox and a team as code owners June 13, 2025 21:36
Copy link

changeset-bot bot commented Jun 13, 2025

🦋 Changeset detected

Latest commit: c7fbbc6

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

This PR includes changesets to release 0 packages

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

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

Copy link

vercel bot commented Jun 13, 2025

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 13, 2025 9:44pm

Copy link
Contributor

coderabbitai bot commented Jun 13, 2025

📝 Walkthrough

Walkthrough

An empty changeset file was added, localization strings for API key time intervals in the English (US) resource file were updated to use more specific placeholders for each time unit, and bundle size limits for certain JavaScript distribution files were slightly increased.

Changes

Files/Groups Change Summary
.changeset/bright-carrots-reply.md Added an empty changeset file containing only YAML front matter delimiters.
packages/localizations/src/en-US.ts Updated API key time interval localization keys to use unit-specific placeholders for each entry.
packages/clerk-js/bundlewatch.config.json Increased maximum allowed bundle sizes slightly for ./dist/clerk.js and ./dist/ui-common*.js.

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2d00b4f and c7fbbc6.

📒 Files selected for processing (1)
  • packages/clerk-js/bundlewatch.config.json (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • packages/clerk-js/bundlewatch.config.json
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Check Permissions
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (actions)
  • GitHub Check: Analyze (javascript-typescript)

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

Comment on lines +1 to +2
---
---
Copy link
Member Author

Choose a reason for hiding this comment

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

safe to skip, we already have changeset for localizations in main API keys PR

@wobsoriano wobsoriano enabled auto-merge (squash) June 13, 2025 21:38
Copy link

pkg-pr-new bot commented Jun 13, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6121

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6121

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6121

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6121

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6121

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6121

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6121

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6121

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6121

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6121

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6121

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6121

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6121

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6121

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6121

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6121

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6121

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6121

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6121

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6121

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6121

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6121

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6121

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6121

commit: c7fbbc6

@wobsoriano wobsoriano merged commit 5b9c672 into main Jun 13, 2025
39 checks passed
@wobsoriano wobsoriano deleted the rob/fix-api-keys-dates branch June 13, 2025 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants