fix(ci): make release zips reproducible and bump version to 0.2.1

adm-zip stamps entries with file mtimes, i.e. the git checkout time on
CI, so two builds of the same commit differed byte-wise and tripped the
immutable no-overwrite guard on workflow re-runs. Pin every entry to the
commit date (SOURCE_DATE_EPOCH convention) instead.

0.2.0 was never published (no manifest entry, no GitHub release), but a
stale chrome-store zip from the first failed run occupies its immutable
slot; move the release to 0.2.1 rather than deleting the object.
This commit is contained in:
go0p
2026-08-18 14:52:48 +08:00
parent c1476a3337
commit 4507c2689d
2 changed files with 12 additions and 1 deletions
+1 -1
View File
@@ -2,7 +2,7 @@
"name": "yakit-chrome-client",
"description": "Yakit Browser Extension",
"private": true,
"version": "0.2.0",
"version": "0.2.1",
"type": "module",
"packageManager": "[email protected]",
"scripts": {