fix(repo): Restore auto PR reviews #7192
Conversation
🦋 Changeset detectedLatest commit: bd15c31 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.
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the WalkthroughA new changeset file is added with placeholder frontmatter, and the CodeRabbit configuration is updated to remove the explicit disabling of auto reviews, allowing the default auto_review behavior to take effect. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
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: |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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/dirty-lizards-arrive.md(1 hunks).coderabbit.yaml(0 hunks)
💤 Files with no reviewable changes (1)
- .coderabbit.yaml
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/**
📄 CodeRabbit inference engine (.cursor/rules/monorepo.mdc)
Automated releases must use Changesets.
Files:
.changeset/dirty-lizards-arrive.md
🪛 LanguageTool
.changeset/dirty-lizards-arrive.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 (localhost, chrome)
- GitHub Check: Integration Tests (quickstart, chrome, 16)
- GitHub Check: Integration Tests (custom, chrome)
- GitHub Check: Integration Tests (nextjs, chrome, 14)
- GitHub Check: Integration Tests (vue, chrome)
- GitHub Check: Integration Tests (nextjs, chrome, 15)
- GitHub Check: Integration Tests (react-router, chrome)
- GitHub Check: Integration Tests (quickstart, chrome, 15)
- GitHub Check: Integration Tests (machine, chrome)
- GitHub Check: Integration Tests (nextjs, chrome, 16)
- GitHub Check: Integration Tests (tanstack-react-start, chrome)
- GitHub Check: Integration Tests (nuxt, chrome)
- GitHub Check: Integration Tests (billing, chrome)
- GitHub Check: Integration Tests (handshake, chrome)
- GitHub Check: Integration Tests (sessions, chrome)
- GitHub Check: Integration Tests (handshake:staging, chrome)
- GitHub Check: Integration Tests (astro, chrome)
- GitHub Check: Integration Tests (elements, chrome)
- GitHub Check: Integration Tests (expo-web, chrome)
- GitHub Check: Integration Tests (sessions:staging, chrome)
- GitHub Check: Integration Tests (ap-flows, chrome)
- GitHub Check: Integration Tests (express, chrome)
- GitHub Check: Integration Tests (generic, chrome)
- GitHub Check: Unit Tests (22, **)
- GitHub Check: Publish with pkg-pr-new
- GitHub Check: Static analysis
- GitHub Check: semgrep-cloud-platform/scan
- GitHub Check: semgrep-cloud-platform/scan
| --- | ||
| --- |
There was a problem hiding this comment.
🧩 Analysis chain
Changeset file is empty — add package and change descriptions.
The changeset file contains only frontmatter markers with no content. Changesets must include package names and descriptions of changes for automated release management.
Add package information and a concise change description between the frontmatter markers. For example:
---
+---
+"@clerk/backend": patch
+---
+Restore auto PR reviewsPlease verify the correct changeset format used in this repository and populate the file accordingly before merging.
🏁 Script executed:
#!/bin/bash
# Examine the specific changeset file and compare with other changesets in the repo
echo "=== Content of dirty-lizards-arrive.md ==="
cat .changeset/dirty-lizards-arrive.md | od -c
echo ""
echo "=== File size ==="
wc -c .changeset/dirty-lizards-arrive.md
echo ""
echo "=== Other changeset files in .changeset/ ==="
fd -e md . .changeset/ --type f | head -10
echo ""
echo "=== Sample of another changeset file ==="
fd -e md . .changeset/ --type f ! -name "dirty-lizards-arrive.md" | head -1 | xargs catLength of output: 653
🌐 Web query:
Changesets format YAML frontmatter package description structure
💡 Result:
Changesets uses a Markdown file with a YAML frontmatter block that maps package names → semver bump types, then a Markdown body that is the changeset description.
Key points
- Location: files live in .changeset/ and are .md files. [1]
- Frontmatter: a YAML block (--- ... ---) where each entry is "package-name": bump. Common bump values: major, minor, patch (other strings are allowed but won’t affect version calculation). Multiple packages may be listed. [1][2]
- Body: the Markdown text after the closing --- is the human-readable summary that appears in changelogs. [1][2]
Minimal example
"@my-org/pkg-a": minor
"@my-org/pkg-b": patch
Add feature X and fix bug Y. [1][2]
Sources
[1] Changesets docs — command-line / add (describes YAML frontmatter, packages, bump types and body).
[2] @changesets/cli README / examples (example .changeset file and explanation).
🏁 Script executed:
#!/bin/bash
# Examine the changeset file from the PR
echo "=== Content of .changeset/dirty-lizards-arrive.md ==="
cat .changeset/dirty-lizards-arrive.md
echo ""
echo "=== File size (bytes) ==="
wc -c < .changeset/dirty-lizards-arrive.md
echo ""
echo "=== Hex dump ==="
hexdump -C .changeset/dirty-lizards-arrive.md
echo ""
echo "=== Other changesets in repo (for format comparison) ==="
find .changeset -name "*.md" ! -name "dirty-lizards-arrive.md" -type f | head -3 | while read f; do
echo "--- $f ---"
cat "$f"
echo ""
doneLength of output: 968
Changeset file is incomplete — add package and change descriptions.
The changeset file .changeset/dirty-lizards-arrive.md contains only frontmatter markers with no content. Changesets requires YAML frontmatter mapping package names to semver bump types, followed by a Markdown body for the changeset description.
The file must include package name(s) and bump type(s) between the frontmatter delimiters, plus a description. For example:
---
"@clerk/backend": patch
---
Restore auto PR reviews
Populate the changeset file with the appropriate package name(s) and change description before merging.
🧰 Tools
🪛 LanguageTool
[grammar] ~1-~1: Hier könnte ein Fehler sein.
Context: --- ---
(QB_NEW_DE)
🤖 Prompt for AI Agents
In .changeset/dirty-lizards-arrive.md around lines 1–2 the file contains only
empty frontmatter; add a YAML mapping between the --- delimiters listing the
package name(s) and their semver bump type (patch/minor/major) and then add a
short Markdown description of the change as the body. Ensure the package names
match your workspace package names, pick the correct bump type for the change,
and save the file so the changeset includes both the frontmatter mapping and a
human-readable description.
Description
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
Summary by CodeRabbit
Release Notes
Note: This release contains no user-facing changes. Updates are limited to internal development tools and build configuration.