deps: bump vgi from 0.24.0 to 0.33.0

[dependabot]

Bumps vgi from 0.24.0 to 0.33.0.

Release notes

Sourced from vgi's releases.

v0.33.0 — VGI 2.0 write result modes

VGI 2.0 write result modes

• Replace per-operation write capability booleans with write_result_modes.
• Replace return_chunks with required result_mode.
• Support the standardized count, rows, and future changes result contracts.
• Published vgi-protocol, vgi, and vgi-client 0.33.0 to crates.io.

v0.32.1

Add argument monotonicity protocol metadata

v0.32.0

Includes the previous commit (Add schema_name to ScanFunctionResult/ ScanBranch). Also applies a cargo fmt fixup to dispatch.rs that the prior commit missed (the release workflows sanity gate runs cargo fmt --all -- --check, which would have failed on it).

v0.31.0

fix(client): enforce subprocess RPC deadlines

v0.30.0

Also fixes the release workflow, which could not have published this tag.

vgi gained a dependency on the vgi-protocol crate when the wire layer was split out after v0.29.0, but the publish step still ran only cargo publish -p vgi. That cannot work: cargo resolves a path+version dependency against the REGISTRY when packaging, and vgi-protocol had never been published — crates.io returns 404 for it. Verified with a local dry-run, which fails with 'no matching package named vgi-protocol found'.

The step now publishes vgi-protocol -> vgi -> vgi-client in dependency order, skipping any version already on crates.io so a re-run after a partial publish completes the remainder instead of needing a version bump.

v0.29.0

The shared landing page now reads the catalog over the VGI protocol instead of fetching a worker-produced describe.json, which this release deletes.

• Workers pass LandingInfo instead of a describe producer; requires vgi-rpc 0.21.0.
• __describe__ now advertises each unary method's real params schema. It previously advertised an empty schema for all 37, which broke any client that builds its request from the advertised shape.
• Attach options gain required, with validation at catalog_attach.

v0.28.0

CopyFromFunction::read returns Vec, so a COPY-FROM reader had to materialize every batch before the scan yielded its first row: peak memory scaled with the whole source, and a multi-GB row file meant a multi-GB buffer.

The scan itself was never the problem. Dispatch already pulls next_batch in a loop and emits each batch to the stream as it arrives, and CopyFromProducer is already a TableProducer sitting on that path — it just filled its entire buffer on the first pull. So this adds a way to plug into the loop that is already

... (truncated)

Commits

• 1beeba7 release: v0.33.0 — VGI 2.0 write result modes (#9)
• 8367355 feat: adopt VGI 2.0 write result modes (#8)
• 70e2821 Add argument monotonicity protocol metadata
• 3a65243 Run worker coverage only on demand (#7)
• 0bb5eef Use the published VGI extension in integration CI (#6)
• db6108b ci: route packaged database worker to Rust fixture (#5)
• 748a45f Add VGI 2 function signature metadata (#3)
• 364db75 Fix Filter v2 integration semantics (#4)
• 19b59dd feat: implement VGI filter encoding v2
• 1b26419 Merge remote-tracking branch 'origin/main' into codex/iroh-framework-parity
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)