- 
                Notifications
    
You must be signed in to change notification settings  - Fork 402
 
fix(shared): Export new types folder for typedoc output #7106
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
base: main
Are you sure you want to change the base?
Conversation
          🦋 Changeset detectedLatest commit: ab8ea9d 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. 
  | 
    
          
WalkthroughUpdated TypeDoc configuration to include generated type files from  Changes
 Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 
 Poem
 Pre-merge checks and finishing touches❌ Failed checks (1 warning)
 ✅ Passed checks (2 passed)
 ✨ Finishing touches🧪 Generate unit tests (beta)
 Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment   | 
    
          
@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:   | 
    
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 (1)
.changeset/tall-melons-switch.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/**
📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)
Automated releases must use Changesets.
Files:
.changeset/tall-melons-switch.md
🪛 LanguageTool
.changeset/tall-melons-switch.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). (5)
- GitHub Check: Formatting | Dedupe | Changeset
 - GitHub Check: Build Packages
 - GitHub Check: Analyze (javascript-typescript)
 - GitHub Check: semgrep-cloud-platform/scan
 - GitHub Check: semgrep-cloud-platform/scan
 
| --- | ||
| --- | 
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 format—missing package metadata and description.
The changeset file is empty. According to the Changesets convention and the coding guidelines requiring automated releases to use Changesets, this file must include:
- Package name and version bump type (e.g., 
@clerk/shared: patch) - A brief description of the change
 
Without this metadata, the release automation will not function correctly.
Based on the PR objectives (moving types and updating exports for TypeDoc), a typical changeset should look like:
 ---
----
+@clerk/shared: patch
+---
+
+Export new types folder for TypeDoc outputPlease update the changeset with the appropriate package name, version bump type (patch/minor/major), and a description of the change.
📝 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: patch | |
| --- | |
| Export new types folder for TypeDoc output | 
🧰 Tools
🪛 LanguageTool
[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- ---
(QB_NEW_DE)
🤖 Prompt for AI Agents
In .changeset/tall-melons-switch.md around lines 1 to 2, the changeset is empty
so release automation will fail; update the file to include the package
identifier and bump type (e.g., "@clerk/shared: patch" or the correct package(s)
and chosen bump level) on the first line and a short descriptive summary on the
following line(s) describing the change (for example: "Move types and update
exports for TypeDoc generation"). Ensure the package name(s), bump type(s), and
a concise description are present and saved.
| 
          
 Found 57 test failures on Blacksmith runners: 
  | 
    
Description
Types were moved from
@clerk/typesto@clerk/shared/types(PR)We need to export the typedoc output from the new
shared/typesfolderChecklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
Summary by CodeRabbit