deps: bump vgi from 0.24.0 to 0.29.0

[dependabot]

Bumps vgi from 0.24.0 to 0.29.0.

Release notes

Sourced from vgi's releases.

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 running:

fn read_stream(&self, ctx) -> Result<Option<Box<dyn TableProducer>>>

Returning None (the default) uses read, so every existing reader is unchanged. A reader that decodes incrementally — an object-store range reader, a File, a socket — returns a producer and holds one batch instead of the file.

NOTHING CHANGES ON THE WIRE. Same RPCs, same batch framing; a worker using the hook is indistinguishable to the extension, and no extension version matters.

Without this a worker can only get streaming by registering its own TableFunction under the COPY handler's name BEFORE register_copy_from, which wins the scan by an overload tie-break (resolve_overload keeps the first candidate on an equal score). That works, but swapping two adjacent registration lines silently reverts it to buffering with no error, and the shadowed registration still shows up in duckdb_functions(). A supported seam is better than a load-bearing accident.

Also fixes two pre-existing rustdoc failures in storage/mod.rs: HttpStorage is exported only under the http-storage feature, so intra-doc links to it could not resolve in a default-feature doc build, and cargo doc -D warnings failed on 0.27.0.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

v0.27.0

The DuckDB extension registers one CopyFunction per alias.format_name and keeps the first registration (vgi_extension.cpp), so a worker advertising a reader and a writer under the same format name silently lost one direction: the second entry hit the registry-first continue and never became a CopyFunction. The extension has always understood direction="both" — only the Rust advertisement could not express it, emitting two independent entries.

... (truncated)

Commits

• 86cda24 style: cargo fmt --all
• 8af1bed release: 0.29.0 — the landing page reads the catalog over the protocol
• ae4c4c6 protocol: advertise every unary method's real params schema
• 6a5a1f1 landing: drop the describe.json producer; advertise wrapped params schemas
• facb502 attach options: add required
• f368c7b release: 0.28.0 — stream COPY FROM via CopyFromFunction::read_stream
• 3e88454 release: 0.27.0 — pair same-named COPY reader/writer into direction="both"
• 6463084 release: 0.26.0 — VGI protocol 1.3.0, global functions, vgi-rpc 0.19.0
• 9616c4d ci(integration): add an executed-case floor (collapse detector)
• 536b58f release: vgi 0.25.0
• 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)