v3.4.0

What's Changed

• Fix critical security issue GHSA-h755-8qp9-cq85 protobufjs Severity Critical 9.8 / 10 by @odselsevier in #252
• Fix pipeline and docker tests by @dependabot in #230
• feature(dependencies): adding support for protobufjs 7 by @kriskw1999 in #271

New Contributors

• @odselsevier made their first contribution in #252
• @kriskw1999 made their first contribution in #271

Full Changelog: v3.3.0...v3.4.0

v3.4.1

What's Changed

• Allow setting full Ajv Instance on JSON options by @pgior001 in #254

New Contributors

• @pgior001 made their first contribution in #254

Full Changelog: v3.4.0...V3.4.1

v3.3.0

[3.3.0] - 2022-10-04

Added

• Support schema references for Avro, Protocol Buffer, and JSON schema #197

Fixed

• Fix Apicurio compatibility with register function #201

v3.2.1

[3.2.1] - 2022-01-28

Fixed

• Don't swallow error message from client-side errors from registry requests #176

v3.2.0

[3.2.0] - 2021-11-22

Added

• Add reader schema option when decoding Avro messages #166

v3.1.1

[3.1.1] - 2021-11-03

Fixed

• Support backwards incompatible changes in Ajv 8 when passing in Ajv instance in JSON Schema options #163

v3.1.0

[3.1.0] - 2021-11-03

Added

• Allow passing in Ajv instance in JSON Schema options #133

Fixed

• Fix backwards compatibility with older Schema Registry versions #158

Fixed

• Fix gateway config for when setting HTTP agent #127

v3.0.1

[3.0.1] - 2021-06-11

Fixed

• Fix gateway config for when setting HTTP agent #127

v3.0.0

This version is non-breaking for the overwhelming majority of users.

When creating an instance of SchemaRegistry for Protobuf without the messageName parameter confluent-schema-registry would, under certain circumstances, default to the wrong message type in the schema. Specifically, instead of defaulting to the first message type in the schema it would erroneously default to the first message type that did not define a nested type.

If you were relying on this behavior may need to either:

• Start passing the messageName parameter instead of relying on the default behavior
• Update your schemas and re-ingest messages accordingly

See issue #112 for more info

Added

• Allow setting HTTP agent #108

Fixed

• Fix default nested Protobuf type #113

v2.0.1

[2.0.1] - 2021-04-02

• Fix export of SchemaType #100