ci

Author: zbeyens

.claude/commands/changeset.md

@@ -44,12 +44,22 @@ The frontmatter is enclosed by ---` lines. It lists each affected package and it
 **Important Note on SemVer Bumping and Multiple Changesets:**
 
 - Each distinct change (breaking, feature, fix) for a package **MUST** have its own changeset file.
+- A single changeset file **MUST** contain only ONE package in its frontmatter.
 - For example, if you make a breaking API change, add a new feature, and fix a bug in `@platejs/core` for an upcoming release, you will create **three separate changeset files**:
   1.  One file marked `major` for `@platejs/core` detailing only the breaking change.
   2.  One file marked `minor` for `@platejs/core` detailing only the new feature.
   3.  One file marked `patch` for `@platejs/core` detailing only the bug fix.
 - The versioning tool will look at all pending changesets for a package. If there's at least one `major` file, the package gets a major version bump, and all changes (from major, minor, and patch files) are included in that release. If no `major` but at least one `minor`, it gets a minor bump, and so on.
 
+**Example: Multiple Changes, Multiple Packages**
+
+- If a PR adds a `minor` feature to `@platejs/core` and a `patch` fix to `@platejs/utils`, you MUST create TWO separate files:
+
+  1.  `core-minor.md` (containing only `'@platejs/core': minor`)
+  2.  `utils-patch.md` (containing only `'@platejs/utils': patch`)
+
+- If a PR adds `minor` features to both `@platejs/core` and `@platejs/utils`, you MUST create TWO separate `minor` changeset files, one for each package. DO NOT group them in a single file.
+
 **Example (Illustrating multiple files for one package):**
 
 File 1: `core-major.md`
@@ -144,29 +154,4 @@ This section explains **what changed for the user** and **how they should adapt*
         ```
         `
 
-- **New Features / Enhancements (`minor` changeset):**
-
-  - - Added `useNewHook()` for managing X.
-    ```ts
-    const value = useNewHook(editor);
-    ```
-  - - Added `newOption` to `PluginName` options for Y.
-  - - Added `editor.meta.containerTypes`: an array of container node types derived from enabled plugins that have `plugin.node.isContainer = true`.
-  - - Updated `editor.api.fragment` to automatically use `editor.meta.containerTypes` as a default for the `containerTypes` option when not explicitly provided.
-
-- **Bug Fixes (`patch` changeset):**
-
-  - - Fixed an issue where typing at the end of a link would not extend the link mark.
-  - - Corrected the behavior of `someFunction()` to prevent crashes with empty inputs.
-
-- **Removals (Always `major`):**
-  - - Removed `obsoleteFunction()` from `**PackageName**`. There is no direct replacement.
-  - - Removed default shortcuts for `**SomePlugin**`. Configure them via `editor.configure(SomePlugin, { shortcuts: { ... } })` if needed.
-
-**Writing Style:**
-
-- **Clarity and Precision:** Be unambiguous.
-- **Action-Oriented:** Use past tense verbs to describe changes. Use imperative mood for migration steps (e.g., "- Replace...", "- Update...").
-- **User-Focused:** Prioritize information crucial for developers integrating the changes.
-
-By strictly following these guidelines, we will maintain a high-quality, accurate, and developer-friendly changelog where each change is distinctly categorized.
+- \*\*New Features / Enhancements (`

.github/workflows/claude-changeset.yml

@@ -3,10 +3,6 @@ name: Claude Changeset
 on:
   issue_comment:
     types: [created]
-  pull_request_review_comment:
-    types: [created]
-  pull_request_review:
-    types: [submitted]
   pull_request:
     types: [opened]
     paths:
@@ -15,14 +11,12 @@ on:
 
 jobs:
   create-changeset:
-    # Only respond to @claude changeset mentions from authorized users in PRs
+    # Only respond to /changeset mentions from authorized users in PRs
     # OR when packages/registry are modified without changesets/changelog updates
     if: |
       (
         (
-          (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude changeset') && github.event.issue.pull_request) ||
-          (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude changeset')) ||
-          (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude changeset'))
+          (github.event_name == 'issue_comment' && contains(github.event.comment.body, '/changeset') && github.event.issue.pull_request)
         ) && (
           github.actor == 'zbeyens' ||
           github.actor == 'felixfeng33'
@@ -98,6 +92,13 @@ jobs:
             - Follow the Changeset Guide (.claude/commands/changeset.md) for structure, naming, and writing style
             - For registry changes, update docs/components/changelog.mdx
 
+            **Critical Requirement: Separate Changesets**
+            - You MUST create a separate changeset file for EACH package AND EACH change type (major, minor, patch).
+            - A single changeset file MUST contain only ONE package in its frontmatter.
+            - **Example 1:** If a PR adds a `minor` feature to `@platejs/core` and a `patch` fix to `@platejs/utils`, you MUST create TWO files: one for `@platejs/core` (minor) and one for `@platejs/utils` (patch).
+            - **Example 2:** If a PR adds `minor` features to both `@platejs/core` and `@platejs/utils`, you MUST create TWO separate `minor` changeset files, one for each package.
+            - This is essential for correct semantic versioning. DO NOT group multiple packages in one file.
+
             **Changeset Standards (for package changes):**
             - Use descriptive file naming: `[package]-[change-type].md`
             - Include proper YAML frontmatter with affected packages and change types
@@ -132,4 +133,8 @@ jobs:
             - One file per distinct change to enable proper SemVer bumping
             - Update changelog.mdx for registry component changes
 
+            **Changeset required when updating packages**
+            - Updating `docs/components/changelog.mdx` is required when updating `apps/www/src/registry`
+            - Use `/docs` command to update documentation
+
             Please analyze the changes in this PR and create appropriate changeset files and/or update the changelog following the guide.

.github/workflows/claude-docs.yml

@@ -3,19 +3,13 @@ name: Claude Docs
 on:
   issue_comment:
     types: [created]
-  pull_request_review_comment:
-    types: [created]
-  pull_request_review:
-    types: [submitted]
 
 jobs:
   update-docs:
-    # Only respond to @claude docs mentions from authorized users in PRs
+    # Only respond to /docs mentions from authorized users in PRs
     if: |
       (
-        (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude docs') && github.event.issue.pull_request) ||
-        (github.event_name == 'pull_request_review_comment' && contains(github.event.comment.body, '@claude docs')) ||
-        (github.event_name == 'pull_request_review' && contains(github.event.review.body, '@claude docs'))
+        (github.event_name == 'issue_comment' && contains(github.event.comment.body, '/docs') && github.event.issue.pull_request)
       ) && (
         github.actor == 'zbeyens' ||
         github.actor == 'felixfeng33'

.github/workflows/claude.yml

@@ -16,7 +16,7 @@ jobs:
     if: |
       (
         (
-          (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude') && !contains(github.event.comment.body, '@claude changeset') && !contains(github.event.comment.body, '@claude docs')) ||
+          (github.event_name == 'issue_comment' && contains(github.event.comment.body, '@claude')) ||
           (github.event_name == 'issues' && contains(github.event.issue.body, '@claude')) ||
           (github.event_name == 'discussion' && contains(github.event.discussion.body, '@claude')) ||
           (github.event_name == 'discussion_comment' && contains(github.event.comment.body, '@claude'))