From ee0408a944e7d3196eed5999d2fa988a911f13ba Mon Sep 17 00:00:00 2001 From: Ubuntu Date: Sat, 23 May 2026 18:56:23 +0800 Subject: [PATCH] fix(ci): sync manifest version from tag before build The release workflow was always building with the hardcoded version from package.json (1.0.0), causing Chrome Web Store to reject uploads because 1.0.0 equals the already-published 1.0 (trailing zeros ignored). Added a step to extract the version from the git tag and update package.json before the build, so the zip contains the correct version. --- .github/workflows/release.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index c8d09c8..7ef29d1 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -91,6 +91,12 @@ jobs: path: node_modules key: ${{ runner.os }}-release-v22-${{ hashFiles('**/package-lock.json') }} + - name: Sync version from tag + run: | + VERSION="${GITHUB_REF_NAME#v}" + echo "Setting version to $VERSION" + npm version "$VERSION" --no-git-tag-version + - name: Build and Zip Extension run: | npm run zip