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.
2026-05-23 18:56:23 +08:00
1 changed files with 6 additions and 0 deletions
@@ -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