Repository navigation
Support maxConcurrency in queue consumer exports - #851
Merged
cpojer merged 2 commits intoNov 17, 2026
Merged
Conversation
cpojer
approved these changes
Nov 17, 2026
cpojer
left a comment
Member
There was a problem hiding this comment.
Thank you for adding this feature!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #850.
Queue files can now export
maxConcurrencyto cap the number of batches Cloudflare processes at once. Void maps it tomax_concurrencyfor native and framework-based direct Cloudflare deploys and for Void-managed deploys, including rollback and recovery. Values must be integer literals from 1 to 250; omitting the export preserves automatic scaling.Adds scanner and manifest validation, regression coverage for both deployment paths and omitted settings, a commented option in
void gen queue, and queue guide examples.Void-managed deployments require platform 1.9.2 or later, so older releases cannot silently ignore the cap. Removing the export clears Void-written concurrency limits from framework deployment config and
void.lock.json, while preserving manually configured limits. Regression coverage verifies rejection of older platforms and removal across repeated deployments and config regeneration.Validation:
vp run test:all: formatting, lint, builds, artifact validation, typechecking, and the full suite passed; 815 test files and 17,458 tests passed (39 skipped).vp run check,vp fmt --check,vp lint, andvp run lint:platform.vp run --cache build:allandnode test/check-playground-build-artifacts.mjs.vp run build:docs.vp run test --base main: 14,972 tests passed (39 skipped).Fresh npm and pnpm packed-consumer smoke checks encountered a dependency mismatch during the Vite build: newly resolved
@cloudflare/vite-plugin@2.0.0-rc.0writes.cloudflare/output/v1, while Void's@cloudflare/build-output-utils@0.9.14looks for.cloudflare/output/v0/config.json. The locked workspace uses2.0.0-beta.v.15and0.9.13; this PR leaves dependency versions unchanged.