Skip to content

Conversation

@LauraBeatris
Copy link
Member

@LauraBeatris LauraBeatris commented Nov 24, 2025

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

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

Summary by CodeRabbit

  • Chores
    • Updated internal release workflow configuration for package version management.

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

@LauraBeatris LauraBeatris self-assigned this Nov 24, 2025
@changeset-bot
Copy link

changeset-bot bot commented Nov 24, 2025

🦋 Changeset detected

Latest commit: ca714d5

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 Nov 24, 2025

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

Project Deployment Preview Comments Updated (UTC)
clerk-js-sandbox Ready Ready Preview Comment Nov 24, 2025 8:07pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 24, 2025

Walkthrough

This PR adds a new changeset file and updates a GitHub Actions workflow to correct the input parameter name for a workflow dispatch call, renaming version to clerkjsVersion to align with expected naming conventions.

Changes

Cohort / File(s) Change Summary
Changeset metadata
\.changeset/green-owls-dress\.md
New changeset file created with YAML document separators
Workflow configuration
\.github/workflows/release\.yml
Updated GitHub Actions workflow dispatch input key from version: clerkjsVersion to clerkjsVersion: clerkjsVersion for the sdk-infra-workers update-pkg-versions job

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

  • Verify the updated input parameter name (clerkjsVersion) matches the expected input in the downstream sdk-infra-workers workflow
  • Confirm the changeset file structure aligns with project conventions

Poem

🐰 A changeset hops in with grace,
The workflow's input finds its place,
From version to clerkjsVersion it flows,
Naming corrections—as every good rabbit knows! 🌟

Pre-merge checks and finishing touches

✅ 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 changes: it specifies that this is a fix updating the release input for clerk-js version updates, which directly corresponds to the workflow input key change from 'version' to 'clerkjsVersion' in the release.yml file.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch laura/fix-release-ci

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

@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 24, 2025

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/elements

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

@clerk/clerk-expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/clerk-react

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

@clerk/react-router

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

@clerk/remix

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/themes

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

@clerk/types

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

@clerk/upgrade

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

@clerk/vue

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

commit: ca714d5

@LauraBeatris LauraBeatris requested a review from a team November 24, 2025 20:10
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

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 26042b8 and ca714d5.

📒 Files selected for processing (2)
  • .changeset/green-owls-dress.md (1 hunks)
  • .github/workflows/release.yml (1 hunks)
⏰ 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). (32)
  • GitHub Check: Integration Tests (quickstart, chrome, 15)
  • GitHub Check: Integration Tests (quickstart, chrome, 16)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (nextjs, chrome, 15, RQ)
  • GitHub Check: Integration Tests (nextjs, chrome, 16)
  • GitHub Check: Integration Tests (machine, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (machine, chrome, RQ)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (custom, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (billing, chrome, RQ)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (handshake, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (handshake:staging, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Integration Tests (sessions:staging, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Publish with pkg-pr-new
  • GitHub Check: Unit Tests (22, shared, clerk-js, RQ)
  • GitHub Check: Static analysis
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
.github/workflows/release.yml (1)

88-88: Parameter name correction is appropriate.

The input key has been corrected from version to clerkjsVersion to align with the expected parameter name in the downstream update-pkg-versions.yml workflow. This fixes the input parameter mismatch and ensures the clerk-js version is passed with the correct key.

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 | 🔴 Critical

Changeset file is malformed and will not be processed.

The changeset file must declare a package name, version bump type, and description. The current file contains only YAML separators with no substantive content.

Populate the changeset file with the proper format:

  ---
+ "@clerk/clerk-js": patch
  ---
+ Fix workflow dispatch input parameter name for clerk-js version update.

Verify the package name (e.g., @clerk/clerk-js or clerk-js) and bump type (major/minor/patch) match the actual changes being released.

📝 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/clerk-js": patch
---
Fix workflow dispatch input parameter name for clerk-js version update.
🤖 Prompt for AI Agents
In .changeset/green-owls-dress.md lines 1-2 the changeset contains only YAML
separators and is malformed; replace the empty file with a proper changeset that
declares the package name, the version bump type (major/minor/patch) and a short
description. Ensure the package name matches the repo package (e.g.,
@clerk/clerk-js or clerk-js), choose the correct bump type for the changes
you’re releasing, and add a clear human-readable description of the change;
remove the stray empty separators so the file is valid YAML frontmatter for the
changeset tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants