Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cloudflare deploy fails when the newest version has no bindings

Closed
  • Is something wrong?
#457 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@aayushbtw is already working on this.

Since Oct 16, 2026.

  • #458 by @aayushbtw — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
cloud

Research direction

Start with the versions.view operation in packages/void/src/cli/cf-version-runner.ts, where the issue says versions without bindings are treated as unreadable. Check the Cloudflare response for a version with no bindings and trace how that affects secret inheritance verification. Done means a binding-free version can be read and deploy proceeds to upload; pull request #458 is already open.

Written by the indexing model from the issue text.

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.

Dominant language
TypeScript
Stars
402
Forks
32
Avg merge
10h 51m
Merged PRs (30d)
100

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/void

All issues in voidzero-dev/void

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.