Skip to content

deps: bump vgi from 0.24.0 to 0.31.0 - #18

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/vgi-0.31.0
Open

deps: bump vgi from 0.24.0 to 0.31.0#18
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/vgi-0.31.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 1, 2026

Copy link
Copy Markdown

Bumps vgi from 0.24.0 to 0.31.0.

Release notes

Sourced from vgi's releases.

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

... (truncated)

Commits
  • 074ae22 fix(client): enforce subprocess RPC deadlines
  • 39d6eeb test(worker): exercise stale-while-revalidate
  • 6d0f77a Use transparent logo and add CI/crates.io badges to README
  • 9e6fd6f fix(worker): consume profiling state after callback
  • 21a2b2a feat(client): expose table profiling callback
  • 13b49ee ci: stamp source-built extension ABI version
  • cf3e893 ci: test against pinned source-built VGI extension
  • 49f3391 test(worker): model split cache revalidation
  • 32022de test(client): preserve global function overloads
  • f06b0db test(worker): exercise qualified macro dependencies
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [vgi](https://github.com/Query-farm/vgi-rust) from 0.24.0 to 0.31.0.
- [Release notes](https://github.com/Query-farm/vgi-rust/releases)
- [Commits](Query-farm/vgi-rust@v0.24.0...v0.31.0)

---
updated-dependencies:
- dependency-name: vgi
  dependency-version: 0.31.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Sep 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants