internal(fix): Gate GitHub releases on hasChangesets instead of published (#3816)

`published == 'true'` is never satisfied because changesets/action
cannot detect publications from the custom `yarn workspaces foreach`
publish command. Use `hasChangesets == 'false'` which reliably indicates
the Version Packages PR was merged and publish executed.

Made-with: Cursor

Author: ntucker

.github/workflows/release.yml

@@ -37,7 +37,12 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
+      # hasChangesets is 'false' after the Version Packages PR is merged (no
+      # changeset files remain), which is the same run where publish executes.
+      # We can't use `published == 'true'` because the custom yarn publish
+      # command isn't detectable by changesets/action.
       - name: Create GitHub Releases
+        if: steps.changesets.outputs.hasChangesets == 'false'
         run: node scripts/create-github-releases.mjs
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

scripts/create-github-releases.mjs

@@ -2,7 +2,8 @@
 /**
  * Creates GitHub releases for published packages.
  * Scans all packages, checks if a release already exists for the current version,
- * and creates one if not. Safe to run on every push (idempotent).
+ * and creates one if not. Gated in CI by `hasChangesets == 'false'` so it only
+ * runs after the Version Packages PR is merged and publish executes.
  */
 import { execSync } from 'child_process';
 import { readdirSync, readFileSync, existsSync } from 'fs';