more ci improvements

Author: chillenious

.github/workflows/release.yml

@@ -17,6 +17,19 @@ on:
       - ".github/workflows/release.yml"
   workflow_dispatch:
     inputs:
+      release_intent:
+        description: "What should this manual run do?"
+        required: true
+        type: choice
+        options:
+          - version-pr
+          - publish
+        default: version-pr
+      force_publish:
+        description: "Allow manual publish even when version-bump detection is false (use for reruns/recovery)"
+        required: false
+        type: boolean
+        default: false
       version_type:
         description: 'Version bump type (major/minor/patch)'
         required: false
@@ -100,18 +113,39 @@ jobs:
 
           echo "has_version_bumps=${has_version_bumps}" >> "$GITHUB_OUTPUT"
 
+      - name: Validate manual release intent prerequisites
+        if: github.event_name == 'workflow_dispatch'
+        shell: bash
+        run: |
+          set -euo pipefail
+          intent="${{ inputs.release_intent }}"
+          has_changesets="${{ steps.detect.outputs.has_changesets }}"
+          has_version_bumps="${{ steps.detect.outputs.has_version_bumps }}"
+          force_publish="${{ inputs.force_publish }}"
+
+          if [ "$intent" = "version-pr" ] && [ "$has_changesets" != "true" ]; then
+            echo "Manual intent 'version-pr' requires at least one .changeset/*.md file in this commit."
+            exit 1
+          fi
+
+          if [ "$intent" = "publish" ] && [ "$has_version_bumps" != "true" ] && [ "$force_publish" != "true" ]; then
+            echo "Manual intent 'publish' requires package.json/CHANGELOG.md version bump changes."
+            echo "If you are rerunning/recovering a failed publish from master, re-run with force_publish=true."
+            exit 1
+          fi
+
       - name: Stop early (no changesets / no version bumps)
         if: github.event_name != 'workflow_dispatch' && steps.detect.outputs.has_changesets != 'true' && steps.detect.outputs.has_version_bumps != 'true'
         run: |
           echo "No .changeset files and no package version/changelog updates in this push. Skipping release."
           exit 0
 
       - name: Build packages (publish runs only)
-        if: github.event_name == 'workflow_dispatch' || steps.detect.outputs.has_version_bumps == 'true'
+        if: (github.event_name == 'workflow_dispatch' && inputs.release_intent == 'publish') || (github.event_name != 'workflow_dispatch' && steps.detect.outputs.has_version_bumps == 'true')
         run: bun run build
 
       - name: Run tests (publish runs only)
-        if: github.event_name == 'workflow_dispatch' || steps.detect.outputs.has_version_bumps == 'true'
+        if: (github.event_name == 'workflow_dispatch' && inputs.release_intent == 'publish') || (github.event_name != 'workflow_dispatch' && steps.detect.outputs.has_version_bumps == 'true')
         run: bun run test
 
       - name: Create Release Pull Request or Publish to NPM

README.md

@@ -104,6 +104,17 @@ Use release labels to tag a coordinated release wave across packages while keepi
 
 `bun run release:label:push` - Create and push the release tag to origin
 
+### Manual Publish Recovery (GitHub Actions)
+
+If a publish fails after the version PR was already merged, rerun the Release workflow manually:
+
+1. Actions → **Release** → **Run workflow**
+2. Branch: `master`
+3. `release_intent`: `publish`
+4. `force_publish`: `true`
+
+This is intended for recovery/rerun scenarios only.
+
 ### Maintainer Commands
 
 `bun cli upstream:sync` - (Maintainers only) Syncs packages from the upstream pie-elements project. Requires pie-elements and pie-lib checked out as sibling directories. Analyzes the current state of those projects and copies over what is ready for ESM packaging, including rewrites and restructuring to fit the new project layout.

docs/ARCHITECTURE.md

@@ -1180,6 +1180,10 @@ Note: `'unsafe-inline'` for styles is required for Svelte scoped styles.
 4. Maintainer merges Version PR
 5. Packages automatically published to npm
 
+If a publish fails after merge, maintainers can manually rerun the Release workflow
+with `release_intent=publish` and `force_publish=true` to recover without creating a
+new version-bump commit.
+
 See [PUBLISHING.md](./PUBLISHING.md) for details (when available).
 
 ### Versioning

scripts/changeset-publish-resolved-workspaces.mjs

@@ -114,7 +114,9 @@ const restoreWorkspaceRanges = () => {
   }
 };
 
-const runChangesetPublish = () =>
+const sleep = (ms) => new Promise((resolve) => setTimeout(resolve, ms));
+
+const runChangesetPublishOnce = () =>
   new Promise((resolve, reject) => {
     const child = spawn('bunx', ['changeset', 'publish'], {
       cwd: repoRoot,
@@ -129,6 +131,30 @@ const runChangesetPublish = () =>
     child.on('error', reject);
   });
 
+const runChangesetPublish = async () => {
+  // Retry once to recover from transient npm issues or partial publishes.
+  // On retry, Changesets skips versions that are already published.
+  const maxAttempts = 2;
+  let lastError;
+
+  for (let attempt = 1; attempt <= maxAttempts; attempt++) {
+    try {
+      console.log(`[release] Running changeset publish (attempt ${attempt}/${maxAttempts})`);
+      await runChangesetPublishOnce();
+      return;
+    } catch (error) {
+      lastError = error;
+      if (attempt === maxAttempts) break;
+      console.warn(
+        `[release] changeset publish failed on attempt ${attempt}; retrying once in 5s...`
+      );
+      await sleep(5000);
+    }
+  }
+
+  throw lastError;
+};
+
 try {
   rewriteWorkspaceRanges();
   if (changedFiles.length > 0) {