search

BEagle1984 / silverback

Silverback is a simple but feature-rich message bus for .NET core (it currently supports Kafka, RabbitMQ and MQTT).
https://silverback-messaging.net
MIT License
259 stars 38 forks source link

chore: bump Confluent.SchemaRegistry.Serdes.Avro from 1.9.3 to 2.0.2 #181

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps Confluent.SchemaRegistry.Serdes.Avro from 1.9.3 to 2.0.2.

Release notes

Sourced from Confluent.SchemaRegistry.Serdes.Avro's releases.

2.0.2

Upgrade considerations

OpenSSL 3.0.x upgrade in librdkafka requires a major version bump, as some legacy ciphers need to be explicitly configured to continue working, but it is highly recommended NOT to use them. The rest of the API remains backward compatible.

Enhancements

  • References librdkafka.redist 2.0.2. Refer to the librdkafka v2.0.0 release notes and later ones for more information.
  • Upgraded NJsonSchema to v10.6.3
  • Added LatestCompatibilityStrict configuration property to JsonSerializerConfig to check the compatibility with latest schema when UseLatestVersion is set to true.
  • Added DeleteConsumerGroupOffset to AdminClient.
  • KIP-222 Finish remaining implementation: Add Consumer Group operations to Admin API (DeleteGroups is already present).
  • KIP-518 Allow listing consumer groups per state.
  • KIP-396 Partially implemented: support for AlterConsumerGroupOffsets.
  • As result of the above KIPs, added (#1981)
    • ListConsumerGroups Admin operation. Supports listing by state.
    • DescribeConsumerGroups Admin operation. Supports multiple groups.
    • ListConsumerGroupOffsets Admin operation. Currently, only supports 1 group with multiple partitions. Supports the requireStable option.
    • AlterConsumerGroupOffsets Admin operation. Currently, only supports 1 group with multiple offsets.

Fixes

  • During a group rebalance, partitions are now always revoked as a side effect of a call to Consume, whether or not a partitions revoked handler has been specified. Previously, if no handler was specified, the timing of when the consumer lost ownership of partitions during a rebalance was arbitrarily, frequently resulting in an erroneous state exception when committing or storing offsets.
  • Fixed 100% CPU usage with DependentAdminClientBuilder.

Note: There were no 2.0.0 and 2.0.1 releases.

Changelog

Sourced from Confluent.SchemaRegistry.Serdes.Avro's changelog.

2.0.2

Upgrade considerations

OpenSSL 3.0.x upgrade in librdkafka requires a major version bump, as some legacy ciphers need to be explicitly configured to continue working, but it is highly recommended NOT to use them. The rest of the API remains backward compatible.

Enhancements

  • References librdkafka.redist 2.0.2. Refer to the librdkafka v2.0.0 release notes and later ones for more information.
  • Upgraded NJsonSchema to v10.6.3
  • Added LatestCompatibilityStrict configuration property to JsonSerializerConfig to check the compatibility with latest schema when UseLatestVersion is set to true.
  • Added DeleteConsumerGroupOffset to AdminClient.
  • KIP-222 Finish remaining implementation: Add Consumer Group operations to Admin API (DeleteGroups is already present).
  • KIP-518 Allow listing consumer groups per state.
  • KIP-396 Partially implemented: support for AlterConsumerGroupOffsets.
  • As result of the above KIPs, added (#1981)
    • ListConsumerGroups Admin operation. Supports listing by state.
    • DescribeConsumerGroups Admin operation. Supports multiple groups.
    • ListConsumerGroupOffsets Admin operation. Currently, only supports 1 group with multiple partitions. Supports the requireStable option.
    • AlterConsumerGroupOffsets Admin operation. Currently, only supports 1 group with multiple offsets.

Fixes

  • During a group rebalance, partitions are now always revoked as a side effect of a call to Consume, whether or not a partitions revoked handler has been specified. Previously, if no handler was specified, the timing of when the consumer lost ownership of partitions during a rebalance was arbitrarily, frequently resulting in an erroneous state exception when committing or storing offsets.
  • Fixed 100% CPU usage with DependentAdminClientBuilder.

Note: There were no 2.0.0 and 2.0.1 releases.

Commits


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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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)
dependabot[bot] commented 1 year ago

Looks like Confluent.SchemaRegistry.Serdes.Avro is up-to-date now, so this is no longer needed.