build: migrate from changesets to semantic-release

.claude/commands/commit.md

@@ -6,6 +6,7 @@ argument-hint: [optional message]
 # Create Git Commit
 
 Create a git commit following Angular/Conventional Commits format.
+This repo uses semantic-release, so commit messages directly drive versioning.
 
 ## Context
 
@@ -27,10 +28,14 @@ type(scope): subject
 
 **Rules:**
 
-- Subject must be max 100 characters
-- Use lowercase for type and scope
+- Header must be <= 100 characters
+- Type and scope must be lowercase
+- Subject must be lowercase
 - No period at the end of subject
 - Use imperative mood: "add feature" not "added feature"
+- Scope is optional, but if used must be one of: `website`, `docs`, `deps`
+  - Use `docs` for README/markdown only changes
+  - Use `website` for `website/` changes
 
 ### Commit Types
 
@@ -53,21 +58,24 @@ type(scope): subject
 Common scopes in this project:
 
 - `website` - website folder changes
+- `docs` - documentation only changes
 - `deps` - Dependencies
+- `cli` - cli folder vsync package changes
 
 ### Examples
 
 ```
 feat(website): add hotel card component
 chore(deps): update React to v19
+docs(docs): update README with new setup instructions
 docs: update README with new setup instructions
 style: format code with prettier
 ```
 
 ## Task
 
 1. If $ARGUMENTS provided, use as commit message hint
-2. Analyze the staged/unstaged changes
-3. Stage relevant files with `git add`
+2. Analyze staged/unstaged changes and choose a single coherent scope
+3. Stage relevant files with `git add` (avoid unrelated files)
 4. Create commit with appropriate type, scope (if applicable), and subject
-5. Keep subject concise (max 100 chars), focus on "what" changed
+5. Keep subject concise (<= 100 chars), focus on "what" changed

.claude/commands/create-pr.md

@@ -3,9 +3,22 @@ description: Create GitHub Pull Request following Angular commit convention
 argument-hint: [optional description]
 ---
 
-# Create Pull Request
+# Create Pull Request (Semantic-release Friendly)
 
-Create a GitHub Pull Request following the project's Angular commit convention.
+Create a GitHub Pull Request that works with semantic-release.
+This repo defaults to **Squash and merge**, so the **PR title becomes the release commit**.
+Therefore the PR title MUST follow Conventional Commits _exactly_:
+
+```
+<type>(<scope>): <subject>
+```
+
+**Hard rules (must pass CI):**
+
+- Subject must be lowercase
+- Subject must NOT end with a period
+- Header length must be <= 100 characters
+- Scope is optional, but if used must be one of: `website`, `docs`, `deps`, `cli`
 
 ## Context
 
@@ -18,39 +31,41 @@ Create a GitHub Pull Request following the project's Angular commit convention.
 
 ## Prerequisites
 
-1. Check if `gh` CLI is available and authenticated:
+1. Ensure `gh` CLI is available and authenticated:
+
    ```bash
    gh auth status
    ```
 
-2. Ensure all changes are committed:
+2. Ensure all changes are committed and branch is pushed:
    ```bash
    git status
+   git push -u origin HEAD
    ```
 
 ## PR Title Format (Angular Convention)
 
-**IMPORTANT**: PR titles MUST follow Angular commit convention. This is enforced by GitHub Action.
+**IMPORTANT**: PR title MUST follow Angular/Conventional Commit format because squash uses it as the release commit.
 
 ```
 <type>(<scope>): <subject>
 ```
 
 ### Types
 
-| Type | Description |
-|------|-------------|
-| `feat` | A new feature |
-| `fix` | A bug fix |
-| `docs` | Documentation only changes |
-| `style` | Changes that do not affect the meaning of the code |
-| `refactor` | A code change that neither fixes a bug nor adds a feature |
-| `perf` | A code change that improves performance |
-| `test` | Adding missing tests or correcting existing tests |
-| `build` | Changes that affect the build system or external dependencies |
-| `ci` | Changes to CI configuration files and scripts |
-| `chore` | Other changes that don't modify src or test files |
-| `revert` | Reverts a previous commit |
+| Type       | Description                                                   |
+| ---------- | ------------------------------------------------------------- |
+| `feat`     | A new feature                                                 |
+| `fix`      | A bug fix                                                     |
+| `docs`     | Documentation only changes                                    |
+| `style`    | Changes that do not affect the meaning of the code            |
+| `refactor` | A code change that neither fixes a bug nor adds a feature     |
+| `perf`     | A code change that improves performance                       |
+| `test`     | Adding missing tests or correcting existing tests             |
+| `build`    | Changes that affect the build system or external dependencies |
+| `ci`       | Changes to CI configuration files and scripts                 |
+| `chore`    | Other changes that don't modify src or test files             |
+| `revert`   | Reverts a previous commit                                     |
 
 ### Scopes (optional)
 
@@ -77,66 +92,50 @@ refactor: simplify authentication logic
 
 ## Creating a Pull Request
 
-### Basic Command
-
-```bash
-gh pr create \
-  --title "feat(website): your descriptive title" \
-  --body "## Description
-
-Brief summary of changes.
+### Fill the PR Template
 
-Fixes #123
-
-## Type of Change
-
-- [x] New feature
-
-## Checklist
+Use `.github/PULL_REQUEST_TEMPLATE.md` as the base. Fill in the summary, fixes, and type.
 
-- [x] Code follows style guidelines
-- [x] Self-review completed
-- [x] No new warnings" \
-  --base main
-```
-
-### Using HEREDOC for Complex Descriptions
+### Recommended Command (template-based)
 
 ```bash
-gh pr create --title "feat(website): add new feature" --body "$(cat <<'EOF'
+gh pr create \
+  --title "feat(scope): short, lowercase summary" \
+  --body "$(cat <<'EOF'
 ## Description
 
-Brief summary of the changes and the motivation behind them.
+Brief summary of the change and why it matters.
 
 Fixes #123
 
 ## Type of Change
 
 - [ ] Bug fix (non-breaking change which fixes an issue)
-- [x] New feature (non-breaking change which adds functionality)
+- [ ] New feature (non-breaking change which adds functionality)
 - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 - [ ] Documentation update
 
 ## Checklist
 
-- [x] My code follows the style guidelines of this project
-- [x] I have performed a self-review of my code
-- [x] I have made corresponding changes to the documentation
-- [x] My changes generate no new warnings
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] Any dependent changes have been merged and published
 
 ## Screenshots (if applicable)
 
 N/A
 EOF
-)" --base main
+)" \
+  --base main
 ```
 
-### Create as Draft
-
-Add `--draft` flag for work in progress:
+### Draft PR (WIP)
 
 ```bash
-gh pr create --title "feat: wip feature" --body "..." --base main --draft
+gh pr create --title "feat(scope): wip summary" --body "WIP" --base main --draft
 ```
 
 ## Useful Commands

.github/workflows/pr-title.yml

@@ -1,8 +1,14 @@
 # =============================================================================
 # PR Title Validation
 # =============================================================================
-# Validates that PR titles follow Angular commit convention.
-# This ensures consistent and meaningful PR titles for changelog generation.
+# Validates PR titles using Conventional Commits (semantic-release friendly).
+# This repo uses **Squash and merge**, so the PR title becomes the release commit.
+# Keeping titles compliant ensures correct version bumps and clean changelogs.
+#
+# Title requirements:
+# - Format: <type>(<scope>): <subject>
+# - Subject: lowercase, no trailing period, <= 100 chars total header
+# - Scope: optional; if present must be one of the allowed scopes below
 #
 # Format: <type>(<scope>): <subject>
 # Example: feat(website): add dark mode toggle
@@ -50,6 +56,7 @@ jobs:
             website
             docs
             deps
+            cli
           # Ensure subject doesn't start with uppercase
           subjectPattern: ^(?![A-Z]).+$
           subjectPatternError: |

.github/workflows/release.yaml

@@ -3,12 +3,6 @@ name: Release
 on:
   push:
     branches: [main]
-    paths:
-      - '.changeset/**'
-      - 'package.json'
-      - 'pnpm-lock.yaml'
-      # optional: include package manifests if you want release to run when versions are bumped
-      - 'cli/package.json'
   workflow_dispatch:
 
 concurrency:
@@ -23,6 +17,18 @@ permissions:
 jobs:
   release:
     runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      max-parallel: 1
+      matrix:
+        package:
+          - name: "@nicepkg/vsync"
+            dir: "cli"
+            copyReadme: "true"
+          # add new packages here
+          # - name: "@nicepkg/vsync-core"
+          #   dir: "core"
+          #   copyReadme: "false"
     steps:
       - uses: actions/checkout@v6
         with:
@@ -31,27 +37,33 @@ jobs:
       - name: Setup Node.js and pnpm
         uses: ./.github/actions/setup-node-pnpm
 
-      - name: Create Release PR or Publish
-        uses: changesets/action@v1
-        with:
-          # use git-cli so symlinks in the repo don't break GitHub API commits
-          commitMode: git-cli
-          setupGitUser: true
-          commit: "chore: version packages"
-          title: "chore: version packages"
-
-          # calculate version + generate changelog + update lockfile (very important)
-          version: pnpm version-packages
-
-          # build before publish (to avoid empty dist)
-          # then publish (you currently use pnpm publish -r)
-          # then tag (to allow action to push tags + create GitHub Releases)
-          publish: bash ./scripts/release-publish.sh
-
-          # explicitly enable GitHub Releases
-          createGithubReleases: true
-
+      - name: Check package exists
+        id: package-check
+        shell: bash
+        run: |
+          if [ -f "${{ matrix.package.dir }}/package.json" ]; then
+            echo "exists=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "exists=false" >> "$GITHUB_OUTPUT"
+          fi
+
+      - name: Copy README files into package
+        if: steps.package-check.outputs.exists == 'true' && matrix.package.copyReadme == 'true'
+        shell: bash
+        run: |
+          cp README.md "${{ matrix.package.dir }}/README.md"
+          cp README_cn.md "${{ matrix.package.dir }}/README_cn.md"
+
+      - name: Build package
+        if: steps.package-check.outputs.exists == 'true'
+        run: pnpm --filter ${{ matrix.package.name }} build
+
+      - name: Run semantic-release
+        if: steps.package-check.outputs.exists == 'true'
+        run: pnpm run semantic-release
         env:
+          SEMREL_PKG_ROOT: ${{ matrix.package.dir }}
+          SEMREL_PKG_NAME: ${{ matrix.package.name }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

.vscode/settings.json

@@ -99,7 +99,7 @@
   "[mdx]": {
     "editor.defaultFormatter": "esbenp.prettier-vscode"
   },
-  "cSpell.words": ["MCPO", "opencode", "vsync"],
+  "cSpell.words": ["MCPO", "nicepkg", "opencode", "SEMREL", "vsync"],
 
   // i18n-ally Configuration for CLI workspace
   "i18n-ally.localesPaths": ["cli/src/locales"],