Skip to content

deps: bump vgi-rpc from 0.16.0 to 0.22.0 - #16

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

deps: bump vgi-rpc from 0.16.0 to 0.22.0#16
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/vgi-rpc-0.22.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 18, 2026

Copy link
Copy Markdown

Bumps vgi-rpc from 0.16.0 to 0.22.0.

Release notes

Sourced from vgi-rpc's releases.

v0.22.0

Fixed

  • A field named with a Rust keyword reached the wire with its r# prefix. #[derive(VgiArrow)] took each column name from Ident::to_string(), which keeps the raw-identifier marker: a field that has to be spelled r#type produced an Arrow column literally named "r#type". The VGI protocol has such a column — catalog_schema_contents_functions and _macros carry a type selector — so those methods could not be called by a Python, C++ or Go peer, which all send type. The prefix is now stripped on both the schema and the array-building path, matching how serde and the rest of the ecosystem treat raw identifiers.

  • Map columns used arrow-rs's child names rather than the protocol's. The Vec<(String, V)> implementation built its entries struct as keys/values — arrow-rs's MapBuilder default — where pyarrow, the canonical Python protocol, the C++ extension and the Go worker all use key/value. Any map-valued field (tags, options, estimated_object_count) therefore went out with non-canonical child names. The read path was already positional, so only what is written changes.

Wire compatibility

Both fixes change bytes on the wire, which is why this is a minor bump rather than a patch. Both move Rust toward the canonical Python protocol, so a Rust worker talking to a Python, C++ or Go peer is strictly more correct after upgrading — one of the two methods above did not work at all before. A Rust-to-Rust pair is unaffected in the map case, since that decoder reads entries positionally.

v0.21.1

Changed

  • The logo is transparent. Both copies of the mark — assets/vgi-logo.png, which the crate READMEs link, and the data: URI inlined in the landing page vgi-rpc serves — were the old export on a white background with no alpha, so both wore a white rectangle wherever the page behind them was not white. Both are now cut from a committed master by scripts/regenerate_logo_assets.py. The inlined copy is palettized to 256 colours, which for flat artwork is visually indistinguishable from truecolour and holds the base64 compiled into every dependent binary at 20 KiB rather than 99 KiB.

No API or wire change; this is a patch.

v0.21.0

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

Breaking: DescribeProvider is removed, replaced by LandingInfo (worker name/doc/version). GET {prefix}/describe.json and the lazy column endpoint are gone; GET {prefix}/vgi-client.js now serves the vendored browser build of @query-farm/vgi, which the page imports same-origin.

... (truncated)

Changelog

Sourced from vgi-rpc's changelog.

[0.22.0] — 2026-08-14

Fixed

  • A field named with a Rust keyword reached the wire with its r# prefix. #[derive(VgiArrow)] took each column name from Ident::to_string(), which keeps the raw-identifier marker: a field that has to be spelled r#type produced an Arrow column literally named "r#type". The VGI protocol has such a column — catalog_schema_contents_functions and _macros carry a type selector — so those methods could not be called by a Python, C++ or Go peer, which all send type. The prefix is now stripped on both the schema and the array-building path, matching how serde and the rest of the ecosystem treat raw identifiers.

  • Map columns used arrow-rs's child names rather than the protocol's. The Vec<(String, V)> implementation built its entries struct as keys/values — arrow-rs's MapBuilder default — where pyarrow, the canonical Python protocol, the C++ extension and the Go worker all use key/value. Any map-valued field (tags, options, estimated_object_count) therefore went out with non-canonical child names. The read path was already positional, so only what is written changes.

Wire compatibility

Both fixes change bytes on the wire, which is why this is a minor bump rather than a patch. Both move Rust toward the canonical Python protocol, so a Rust worker talking to a Python, C++ or Go peer is strictly more correct after upgrading — one of the two methods above did not work at all before. A Rust-to-Rust pair is unaffected in the map case, since that decoder reads entries positionally.

[0.21.1] — 2026-08-13

Changed

  • The logo is transparent. Both copies of the mark — assets/vgi-logo.png, which the crate READMEs link, and the data: URI inlined in the landing page vgi-rpc serves — were the old export on a white background with no alpha, so both wore a white rectangle wherever the page behind them was not white. Both are now cut from a committed master by scripts/regenerate_logo_assets.py. The inlined copy is palettized to 256 colours, which for flat artwork is visually indistinguishable from truecolour and holds the base64 compiled into every dependent binary at 20 KiB rather than 99 KiB.

No API or wire change; this is a patch.

[0.20.0] — 2026-08-05

Added

... (truncated)

Commits
  • fad0b83 release: 0.22.0 — raw identifiers and map child names reach the wire correctly
  • a44c493 release: 0.21.1 — the logo is transparent
  • 798d78b brand: reroll the logo from the new transparent master
  • c30c497 release: bump internal dep pins to 0.21.0
  • 0d1c5b7 release: 0.21.0 — the landing page reads the catalog over the protocol
  • 13b124e http: serve the VGI client bundle; drop the describe.json routes
  • fc97ccd release: 0.20.0 — payloads over 2 GiB survive the socket transports
  • ed07b97 ci: give the large-payload group a step the access log cannot kill
  • 02883d8 fix: bound every transport write, and stop capping legitimate bodies at 256 MiB
  • 4d01aa2 release: 0.19.0
  • 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-rpc](https://github.com/Query-farm/vgi-rpc-rust) from 0.16.0 to 0.22.0.
- [Release notes](https://github.com/Query-farm/vgi-rpc-rust/releases)
- [Changelog](https://github.com/Query-farm/vgi-rpc-rust/blob/main/CHANGELOG.md)
- [Commits](Query-farm/vgi-rpc-rust@v0.16.0...v0.22.0)

---
updated-dependencies:
- dependency-name: vgi-rpc
  dependency-version: 0.22.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 Aug 18, 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