Skip to content

build(deps): bump schema_registry_converter from 4.10.0 to 5.1.0 - #64

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/schema_registry_converter-5.1.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/schema_registry_converter-5.1.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Bumps schema_registry_converter from 4.10.0 to 5.1.0.

Release notes

Sourced from schema_registry_converter's releases.

v5.1.0

What's Changed

New Contributors

Full Changelog: gklijs/schema_registry_converter@v5.0.0...v5.1.0

Big new release closing all the pending issues.

What's Changed

Full Changelog: gklijs/schema_registry_converter@v4.10.0...v5.0.0

Changelog

Sourced from schema_registry_converter's changelog.

5.1.0

New async APIs for getting at the schemas themselves, not just the decoded values:

Expose a decoder's own schema lookup: AvroDecoder::get_schema(id) and JsonDecoder::get_schema(id) (async) are now public, returning the fully self-contained, reference-resolved AvroSchema/JsonSchema for an id, using (and populating) that decoder's cache.

Add fetching a schema by an explicit subject and version, independent of any SubjectNameStrategy: async_impl::schema_registry::get_schema_by_subject_and_version(sr_settings, subject, version) (None for "latest") returns the RegisteredSchema, which can be resolved into a self-contained schema with the new async_impl::avro::get_avro_schema or async_impl::json::get_json_schema.

Add AvroDecoder::decode_with_schema_with_header_id (async), the header-aware counterpart of decode_with_schema, returning the full DecodeResultWithSchema for a message that may carry its schema id/guid in a Kafka header. See #139.

ProtoDecoder (async) now returns the root RegisteredSchema (id, version, properties, tags, ...) as a new schema field on DecodeContext, and gains decode_with_context_and_header_id, the header-aware counterpart of decode_with_context. Note: DecodeContext gaining a public field is breaking if you construct one via struct-literal syntax, or destructure one exhaustively without ..; normal usage, which only reads a DecodeContext returned by the decoder, is unaffected.

5.0.0

Two breaking changes bump this to a major version:

BytesResult (in schema_registry_common) now borrows the payload instead of owning it -- Invalid(Vec<u8>) / Valid(u32, Vec<u8>) are now Invalid(&'a [u8]) / Valid(u32, &'a [u8]), and get_bytes_result returns BytesResult<'_> borrowing from its input, instead of copying the whole payload into a fresh Vec on every call. This is on the hot path of every decode, for every format (Avro, JSON, protobuf), so it matters more the larger your messages are -- see #190 for measurements.

This only affects code that calls get_bytes_result/matches on BytesResult directly. The built-in AvroDecoder, JsonDecoder, ProtoDecoder and ProtoRawDecoder (blocking and async) are not affected -- their decode/decode_with_schema/etc. signatures haven't changed, and existing code calling those is unaffected. If you do call get_bytes_result directly and need to keep the bytes beyond the immediate match (store them, return them, carry them across an .await), copy them out explicitly where you used to get an owned Vec for free:

match get_bytes_result(bytes) {
    BytesResult::Valid(id, bytes) => {
        let owned: Vec<u8> = bytes.to_vec();
        // ... use `owned` instead of `bytes` wherever it needs to outlive this match
    }
    BytesResult::Invalid(bytes) => {
</tr></table> 

... (truncated)

Commits
  • 7e4a817 Prepare the 5.1.0 release.
  • d88bf55 feat: add ProtoDecoder::decode_with_context_and_header_id
  • 098eef3 chore: allium update
  • 57f710a test: adjust/new cases
  • 9f073b7 feat: return schema from proto decoder
  • 6806bca test: new cases
  • ffec88a feat: expose schemas by subject_version
  • 325beff test: new method
  • 2af8196 feat: add AvroDecoder::decode_with_schema_with_header_id
  • bdb264a feat: fetch a typed schema by ID
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Oct 16, 2026
Bumps [schema_registry_converter](https://github.com/gklijs/schema_registry_converter) from 4.10.0 to 5.1.0.
- [Release notes](https://github.com/gklijs/schema_registry_converter/releases)
- [Changelog](https://github.com/gklijs/schema_registry_converter/blob/main/RELEASE_NOTES.md)
- [Commits](gklijs/schema_registry_converter@v4.10.0...v5.1.0)

---
updated-dependencies:
- dependency-name: schema_registry_converter
  dependency-version: 5.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot
dependabot Bot force-pushed the dependabot/cargo/schema_registry_converter-5.1.0 branch from e5c3ed1 to 6e53223 Compare October 21, 2026 08:02
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