Skip to content

fix(repo): Restore auto PR reviews #7192

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Nov 10, 2025
Merged

fix(repo): Restore auto PR reviews #7192

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
84230fc
fix(repo): Restore auto PR reviews
dstaley Nov 10, 2025
62dc788
chore(repo): changeset
dstaley Nov 10, 2025
bd15c31
chore(repo): dudpe lockfile
dstaley Nov 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .changeset/dirty-lizards-arrive.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
---
---
Comment on lines +1 to +2
Copy link
Contributor

@coderabbitai coderabbitai bot Nov 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 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 reviews

Please 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 cat

Length 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 ""
done

Length 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.

1 change: 0 additions & 1 deletion .coderabbit.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
reviews:
auto_review:
enabled: false
ignore_title_keywords:
- 'ci(repo): Version packages'
Loading
Loading