fix(ci): work around changesets/action cwd bug for cli release

changesets/action@v1's early "is there a .changeset directory?" check
ignores its own \`cwd\` input and looks at the workspace root. Since
ours lives at cli/.changeset/, the action errored out before doing
anything useful.

Workaround: symlink .changeset → cli/.changeset at the root in the
workflow, and gitignore that root path so a slip-up never commits the
symlink. version + publish still run with cwd=cli, so they see the
real directory.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: ablaszkiewicz

.github/workflows/cli-release.yml

@@ -48,6 +48,15 @@ jobs:
       - name: Build
         run: pnpm build
 
+      # changesets/action@v1's early state check looks at the workspace root
+      # for `.changeset/`, ignoring its own `cwd` input. We keep changesets in
+      # cli/.changeset/, so symlink it at the root just to satisfy that check.
+      # The symlink is gitignored (see /.gitignore) so the action's commit step
+      # won't pick it up.
+      - name: Symlink .changeset to root for changesets/action
+        working-directory: ${{ github.workspace }}
+        run: ln -s cli/.changeset .changeset
+
       - name: Create release PR or publish to npm
         uses: changesets/action@v1
         with:

.gitignore

@@ -1,2 +1,7 @@
 .cursor/
 .security-audit/
+
+# changesets/action's early state check ignores its own `cwd` input and looks
+# at the workspace root, so cli-release.yml symlinks .changeset → cli/.changeset
+# at the start of the run. This makes sure a slip-up never commits the symlink.
+/.changeset