Repository navigation
Cloudflare deploy fails when the newest version has no bindings #457
Description
void deploy --platform cloudflare stops before uploading when the Worker's newest version has no bindings:
◇ Checking the current Worker deployment...
■ deploy: could not verify which Worker Version would supply inherited secrets; production traffic is unchanged.
cf workers versions get leaves out bindings for a version that has none. The versions.view operation in packages/void/src/cli/cf-version-runner.ts requires bindings to be an array, so it reports the version as unreadable and the secret-inheritance check stops.
I got such a version when a build ran through vp run build, which drops Void's deploy env vars, so the upload had no __VOID_VERSION_METADATA binding. A version that another tool uploaded without bindings would cause the same failure.
Fix: #458
void 1.1.11, cf 1.0.0-beta.17, direct Cloudflare target.
Activity
[-]Cloudflare deploy fails with 'could not verify which Worker Version would supply inherited secrets' on Workers with more than 10 versions[/-][+]Cloudflare deploy misreads version history past 10 versions[/+][-]Cloudflare deploy misreads version history past 10 versions[/-][+]Cloudflare deploy: 'could not verify which Worker Version would supply inherited secrets' after a Void version is active[/+][-]Cloudflare deploy: 'could not verify which Worker Version would supply inherited secrets' after a Void version is active[/-][+]Cloudflare deploy: inherited-secrets check fails in CI[/+][-]Cloudflare deploy: inherited-secrets check fails in CI[/-][+]Cloudflare deploy fails when the newest version has no bindings[/+]fix(docs): patch void for versions without bindings
build(docs): drop void patch
fix(deploy): read Cloudflare versions that have no bindings (voidzero…