Compare commits

...

2 Commits

Author SHA1 Message Date
雨霖铃 037e98cd45 fix(tsconfig): remove unused baseUrl and paths configuration 2026-05-24 08:42:43 +08:00
LingandRX 6abdf4add4 fix(ci): sync manifest version from tag before build (#49)
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.

Co-authored-by: Ubuntu <ubuntu@localhost.localdomain>
2026-05-23 18:58:08 +08:00
2 changed files with 7 additions and 5 deletions
+6
View File
@@ -91,6 +91,12 @@ jobs:
path: node_modules path: node_modules
key: ${{ runner.os }}-release-v22-${{ hashFiles('**/package-lock.json') }} 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 - name: Build and Zip Extension
run: | run: |
npm run zip npm run zip
+1 -5
View File
@@ -26,11 +26,7 @@
"target": "ESNext", "target": "ESNext",
"types": ["chrome", "webextension-polyfill", "@testing-library/jest-dom", "vitest/globals"], "types": ["chrome", "webextension-polyfill", "@testing-library/jest-dom", "vitest/globals"],
"noImplicitAny": true, "noImplicitAny": true
"baseUrl": ".",
"paths": {
"@/*": ["./*"]
}
}, },
// 确保包含你的源代码目录 // 确保包含你的源代码目录
"include": [ "include": [