From 33d4a8f235edbf4679fefdb687400e653f35fdb4 Mon Sep 17 00:00:00 2001 From: ZN-Ice Date: Sun, 19 Jul 2026 15:01:25 +0800 Subject: [PATCH] fix(release): drop detached-HEAD version-commit step MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "Commit version changes" step ran `git push` after checking out the release tag, which is a detached HEAD — so it failed every release with `fatal: You are not currently on a branch.` (exit 128). This made the macOS job red on every release even though build, asset upload, and npm publish all succeeded before it. Remove the step. release-pipeline.md already states that packages/*/package.json versions lagging the published npm versions is "expected and harmless" — CI rewrites them at publish time from the tag, so committing them back to main is unnecessary (and impossible from a detached HEAD anyway). Co-Authored-By: Claude --- .github/workflows/release.yml | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index caf7b90..daa5716 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -199,18 +199,6 @@ jobs: npm publish ./packages/cli-box-electron-darwin-arm64 --access public npm publish ./packages/cli-box-skill --access public - - name: Commit version changes - if: github.event_name == 'release' - run: | - git config user.name "github-actions[bot]" - git config user.email "github-actions[bot]@users.noreply.github.com" - git add packages/cli-box-darwin-arm64/package.json \ - packages/cli-box-electron-darwin-arm64/package.json \ - packages/cli-box-linux-x64/package.json \ - packages/cli-box-skill/package.json - git diff --cached --quiet || git commit -m "chore(npm): bump package versions to ${GITHUB_REF_NAME#v}" - git push - build-linux: name: Build Linux (headless) runs-on: ubuntu-latest