fix: resilient publish — idempotent commit/tag/push

- Skip commit if package.json already at target version
- Force-update tag (handles retry after partial failure)
- Push commit and tag separately to avoid partial failures

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: BrainSlugs83

.github/workflows/publish.yml

@@ -31,20 +31,21 @@ jobs:
 
       - run: npm run check
 
-      # Commit version bump, tag, and push
-      - name: Commit and tag
+      # Commit version bump (if changed), tag, and push
+      - name: Commit, tag, and push
         run: |
           git config user.name "github-actions[bot]"
           git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
           git add package.json package-lock.json
-          git commit -m "v${{ inputs.version }}"
-          git tag "v${{ inputs.version }}"
-          git push origin main --tags
+          git diff --cached --quiet || git commit -m "v${{ inputs.version }}"
+          git tag -f "v${{ inputs.version }}"
+          git push origin main
+          git push origin "v${{ inputs.version }}" --force
 
       # Create GitHub Release from the new tag
       - name: Create GitHub Release
         env:
           GH_TOKEN: ${{ github.token }}
-        run: gh release create "v${{ inputs.version }}" --generate-notes
+        run: gh release create "v${{ inputs.version }}" --generate-notes --latest
 
       - run: npm publish --provenance --access public