wuzf ca0e495ab4 fix(deploy): make KV detection env-aware to prevent misreporting ...

Step 2.5 in deploy.js was env-blind, so 'npm run deploy:dev' falsely
reported reusing the production KV while wrangler silently fell back to
the env binding. Combined with [env.development] inheriting top-level
routes, dev deploys could also hijack the production custom domain.
Make extractWorkerName / injectKvNamespaceId / findExistingKvId accept
an envName parameter, and preserve [env.development].routes across
Sync Upstream merges so 'routes = []' overrides survive upgrades.

2026-05-10 11:02:12 +08:00

..

build-release.js

chore(release): v1.4.0

2026-04-19 01:28:21 +08:00

deploy-config.js

fix(deploy): make KV detection env-aware to prevent misreporting

2026-05-10 11:02:12 +08:00

deploy.js

fix(deploy): make KV detection env-aware to prevent misreporting

2026-05-10 11:02:12 +08:00

generate-version.js

feat: restructure into modular architecture with full open-source setup

2025-06-07 23:31:55 +08:00

merge-wrangler-config.js

fix(deploy): make KV detection env-aware to prevent misreporting

2026-05-10 11:02:12 +08:00

patch-serviceworker.js

feat: restructure into modular architecture with full open-source setup

2025-06-07 23:31:55 +08:00