Skip to content

Conversation

@jacekradko
Copy link
Member

@jacekradko jacekradko commented Jan 24, 2026

Summary

  • Fix formatting issues in es-ES localization file

Test plan

  • N/A - formatting only changes

Summary by CodeRabbit

  • Chores
    • Refined Spanish localization string formatting for consistency.

✏️ Tip: You can customize this high-level summary in your review settings.

@changeset-bot
Copy link

changeset-bot bot commented Jan 24, 2026

🦋 Changeset detected

Latest commit: 8b438ed

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

@vercel
Copy link

vercel bot commented Jan 24, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
clerk-js-sandbox Ready Ready Preview, Comment Jan 24, 2026 4:33am

Request Review

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jan 24, 2026

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/react

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

@clerk/react-router

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@7672

@clerk/upgrade

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

@clerk/vue

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

commit: 8b438ed

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 24, 2026

📝 Walkthrough

Walkthrough

This pull request introduces a changeset file and updates Spanish localization resources. The changeset file .changeset/shiny-signs-tickle.md contains placeholder YAML front matter. The es-ES.ts localization file has been modified with adjustments to string formatting, including consolidating the cannotSubscribeUnrecoverable value from a multi-line to a single-line string, while the emailForm.subtitle value is adjusted but retains equivalent content. Overall, the changes consist of minor text formatting updates to the Spanish localization resource.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: fixing formatting issues in the es-ES localization file, which aligns with both the file modifications and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

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

🤖 Fix all issues with AI agents
In @.changeset/shiny-signs-tickle.md:
- Around line 1-2: The changeset file has empty front matter which fails
validation; open the .changeset markdown and add valid YAML front matter that
lists at least one affected package and a bump type (major/minor/patch), e.g.
provide a packages array with the package name(s) and a type field;
alternatively delete the changeset file if no release is required. Make sure the
front matter is valid YAML (--- delimited) and includes the package
identifier(s) and bump type so Changesets tooling can validate it.

Comment on lines +1 to +2
---
---
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 | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

cat -n .changeset/shiny-signs-tickle.md

Repository: clerk/javascript

Length of output: 81


🏁 Script executed:

# Check if there's any Changesets configuration to understand validation requirements
fd -t f "^(changeset|changelog)" --glob ".changeset*" . | head -20

Repository: clerk/javascript

Length of output: 117


🏁 Script executed:

# Look for any Changesets documentation or config files
find . -name ".changesetrc*" -o -name "changeset.config.*" -o -name ".changelogrc*" 2>/dev/null | head -10

Repository: clerk/javascript

Length of output: 42


🏁 Script executed:

# Find changeset config or package.json to understand the Changesets setup
fd -t f "package.json" . | head -5 | xargs grep -l "changesets" 2>/dev/null

Repository: clerk/javascript

Length of output: 44


🏁 Script executed:

# Look for changeset config files with broader search
find . -maxdepth 2 -type f \( -name ".changesetrc*" -o -name ".changeset" \)

Repository: clerk/javascript

Length of output: 42


🏁 Script executed:

# Check for any example changesets or documentation in .changeset directory
ls -la .changeset/ 2>/dev/null | head -20

Repository: clerk/javascript

Length of output: 1372


🏁 Script executed:

cat -n .changeset/README.md

Repository: clerk/javascript

Length of output: 625


🏁 Script executed:

# Look at a valid changeset example
cat -n .changeset/afraid-apes-cough.md

Repository: clerk/javascript

Length of output: 240


🏁 Script executed:

# Check another example to confirm the pattern
cat -n .changeset/bright-zebras-arrive.md

Repository: clerk/javascript

Length of output: 382


Populate the changeset front matter (empty changeset will fail Changesets validation).

A changeset must declare at least one affected package and bump type; an empty front matter is invalid and breaks Changesets tooling. Please fill it in or remove the file if a changeset isn't required.

✅ Example fix
 ---
+'@clerk/localizations': patch
 ---
+Fix es-ES formatting.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
---
---
---
'@clerk/localizations': patch
---
Fix es-ES formatting.
🤖 Prompt for AI Agents
In @.changeset/shiny-signs-tickle.md around lines 1 - 2, The changeset file has
empty front matter which fails validation; open the .changeset markdown and add
valid YAML front matter that lists at least one affected package and a bump type
(major/minor/patch), e.g. provide a packages array with the package name(s) and
a type field; alternatively delete the changeset file if no release is required.
Make sure the front matter is valid YAML (--- delimited) and includes the
package identifier(s) and bump type so Changesets tooling can validate it.

@jacekradko jacekradko merged commit 738cfc7 into main Jan 24, 2026
59 of 66 checks passed
@jacekradko jacekradko deleted the jacekradko/fix-es-es-formatting branch January 24, 2026 04:53
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