archive/yaklang-chrome-extension
1
0
Fork 0
mirror of https://github.com/yaklang/yaklang-chrome-extension.git synced 2026-09-24 20:21:53 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
123 Commits 7 Branches 16 Tags
master
Commit Graph
3 Commits
Author SHA1 Message Date
go0p d35912c7cf feat: support tab-wide recording and release notes
CI / Test and build (push) Waiting to run
Details
2026-09-24 14:50:33 +08:00
go0p a729251c9c fix(ci): accept the CDN's effective manifest cache window 
The CDN in front of aliyun-oss.yaklang.com rewrites JSON responses to
max-age=60 (the browser-binaries manifest gets the same), which is
stricter than the 300s we set at upload. Assert the effective window is
short rather than matching the upload value.
 2026-08-18 15:04:05 +08:00
go0p 78b0c6befd ci: rebuild release pipeline around OSS manifest protocol 
Replace the broken yarn/Node 18 release workflow (wrong package manager,
missing build/ dir, archived actions) with a manifest-based distribution
flow modeled on yaklang/browser-binaries-mirror:

- scripts/package-release.mjs: package the four variants, emit
  release-entry.json and per-artifact sha256 checksums
- scripts/build-manifest.mjs: merge into a bounded public manifest
  (10 versions) with invariant validation
- scripts/publish-oss.mjs: immutable artifacts (forbid-overwrite,
  one-year cache) and mutable manifest (5-minute cache, checksum
  published second), idempotent via head + sha256 comparison
- scripts/verify-public.mjs: post-publish verification from the public
  endpoint (bytes, headers, zip layout)
- release.yml: pnpm + Node 22, full verify:production, OSS publish,
  GitHub Release, separate public verify job, publish concurrency group
- ci.yml: run verify:production on push/PR
- single-source the extension version in package.json (wxt.config reads)
- document the distribution protocol in README
 2026-08-18 14:40:36 +08:00