-
Notifications
You must be signed in to change notification settings - Fork 406
chore(repo): Update rules for types #7196
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
Conversation
🦋 Changeset detectedLatest commit: 16f3429 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen 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 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughThis PR adds a new empty changeset file and expands monorepo documentation with detailed guidance on package categories, development workflows, testing architecture, build systems, environment configuration, localization support, package dependencies, and release management. No functional code changes introduced. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this 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.
📒 Files selected for processing (2)
.changeset/wild-animals-call.md(1 hunks).cursor/rules/monorepo.mdc(7 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
.changeset/**
📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)
Automated releases must use Changesets.
Files:
.changeset/wild-animals-call.md
.cursor/rules/**
📄 CodeRabbit inference engine (.cursor/rules/global.mdc)
Additional rule files for specific domains should be placed under .cursor/rules/
Files:
.cursor/rules/monorepo.mdc
🪛 LanguageTool
.changeset/wild-animals-call.md
[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- ---
(QB_NEW_DE)
⏰ 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). (28)
- 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, 16)
- GitHub Check: Integration Tests (machine, chrome)
- GitHub Check: Integration Tests (nextjs, chrome, 14)
- GitHub Check: Integration Tests (custom, chrome)
- GitHub Check: Integration Tests (nuxt, chrome)
- GitHub Check: Integration Tests (expo-web, chrome)
- GitHub Check: Integration Tests (billing, chrome)
- GitHub Check: Integration Tests (vue, chrome)
- GitHub Check: Integration Tests (handshake:staging, chrome)
- GitHub Check: Integration Tests (elements, chrome)
- GitHub Check: Integration Tests (sessions:staging, chrome)
- GitHub Check: Integration Tests (astro, chrome)
- GitHub Check: Integration Tests (tanstack-react-start, chrome)
- GitHub Check: Integration Tests (express, chrome)
- GitHub Check: Integration Tests (generic, chrome)
- GitHub Check: Integration Tests (handshake, chrome)
- GitHub Check: Integration Tests (sessions, chrome)
- GitHub Check: Integration Tests (localhost, chrome)
- GitHub Check: Integration Tests (ap-flows, chrome)
- GitHub Check: Unit Tests (22, **)
- GitHub Check: Publish with pkg-pr-new
- GitHub Check: Static analysis
- GitHub Check: Formatting | Dedupe | Changeset
- GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (3)
.cursor/rules/monorepo.mdc (3)
1-5: Front-matter structure and alwaysApply rule preserved correctly.The
alwaysApply: truedirective at line 4 is properly maintained, ensuring these Cursor rules are consistently applied across the monorepo. The description and globs additions provide helpful context for AI agents.Please verify that the glob patterns on line 3 (if present and modified) correctly target the intended file scope for this rule set.
94-96: Excellent addition: Type error resolution guidance directly addresses PR objectives.Lines 94–96 add the critical guidance referenced in the PR objectives: clarifying the
@clerk/shared/typesvs.@clerk/typesdistinction, deprecating the latter, and providing the exact build command (turbo build --filter=@clerk/shared --filter=@clerk/types) for agents to recover from type-related build failures. This will significantly improve agent performance when encountering type errors requiring package rebuilds.
7-107: Documentation content is comprehensive and well-organized.The expanded sections (Repository Overview, Core Package Categories, Directory Structure, Development Workflow, Framework-Specific Packages, Testing Architecture, Build System, Environment Configuration, Localization Support, and Release Management) provide thorough guidance for agents navigating the monorepo. Content is clear, structured logically, and actionable.
| --- | ||
| --- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incomplete changeset: missing required metadata and description.
Changeset files require package metadata and a description to support automated releases. The current file contains only YAML separators with no content between them.
A valid changeset should follow this structure:
---
+"@clerk/shared": minor
+"@clerk/types": minor
---
+
+Update Cursor rules to use @clerk/shared/types and add guidance for resolving type errors.Reference the Changesets documentation for required format.
📝 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.
| --- | |
| --- | |
| --- | |
| @clerk/shared: minor | |
| @clerk/types: minor | |
| --- | |
| Update Cursor rules to use @clerk/shared/types and add guidance for resolving type errors. |
🧰 Tools
🪛 LanguageTool
[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- ---
(QB_NEW_DE)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Empty changesets like this are a specific action. They do not need to be called out as incomplete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dstaley, thank you for the clarification! I understand now that empty changesets with only YAML separators serve a specific purpose in your workflow. I'll make note of this to avoid flagging them as incomplete in future reviews.
(\__/)
(•ㅅ•)
/ >📝 *Taking notes!*
✏️ Learnings added
Learnt from: dstaley
Repo: clerk/javascript PR: 7196
File: .changeset/wild-animals-call.md:1-2
Timestamp: 2025-11-10T17:43:09.237Z
Learning: In the clerk/javascript repository, empty changeset files (containing only "---\n---" with no content) are intentional and serve a specific action. These should not be flagged as incomplete or requiring metadata and description.
Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/elements
@clerk/clerk-expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/clerk-react
@clerk/react-router
@clerk/remix
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/themes
@clerk/types
@clerk/upgrade
@clerk/vue
commit: |
|
Found 6 test failures on Blacksmith runners:
|
Description
This PR updates our always-applied Cursor rules to use
@clerk/shared/types, and how to update the package if a type error occurs. This should (hopefully!) improve agent performance when encountering type errors that arise as a result of needing to build the@clerk/sharedpackage.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
Summary by CodeRabbit
Documentation
Chores