You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
First deploy after void secret put fails with Cloudflare 100405 (exports differ) on a Durable Object Worker #460
On a Worker with Durable Objects, the first void deploy --platform cloudflare after void secret put fails when Void stages the new version at 0% beside the secret-changed one:
■ deploy: Cloudflare could not stage the uploaded Worker Version at zero-percent traffic (exit 1); production traffic is unchanged. Cloudflare error code: 100405.
│ [100405] All versions in a multi-version deployment must declare identical `exports`. Deploy the version that changes `exports` at 100% first, then split traffic.
Repro (unmodified void 1.1.11; a fresh Worker each time; ~670 KB, so the 1 MiB read-back in #459 is not involved):
void deploy a new Worker with two SQLite Durable Object classes (defineDurableObject), routes, two defineScheduled crons, preview_urls: false and a version_metadata binding: succeeds.
void secret put JEV_API_KEY (declared optional in env.ts): succeeds.
void deploy with no code change: fails as above, and so does every retry.
The same code was rebuilt between steps 1 and 3, so the exports shouldn't differ; it looks like the version created by the secret change declares different exports from a version Void uploads. An older Worker of ours did deploy after secret changes, so it may depend on something about a fresh Worker's first versions, but we haven't narrowed that down.
Found while looking into #459. void 1.1.11, cf CLI bundled with it, Node 24.18, macOS.
Activity