2.5.0

New Features

• A more generic format for storing the OpenTelemetry trace context information in an AMQP 1.0 message can now be
  configured, writing the corresponding properties in the message application properties. This is for example relevant
  when using AMQP 1.0 messaging in connection with Eclipse Ditto, resulting in combined traces of Hono and Ditto.
  Please refer to the ${prefix}.useLegacyTraceContextFormat connection property documentation in the
  Hono Client Configuration Guide for additional information.
• The JDBC based Device Registry implementation now has limited support for filter criteria when searching devices.
  Please refer to the Device Registry User Guide for details.
• The Device Registry Management API's search Devices operation now supports restricting the result set to gateway or
  edge devices only using the newly added isGateway query parameter.

Fixes & Enhancements

• When running in a Kubernetes cluster with nodes using cgroups v2, the hono.command_internal.* Kafka topics were not
  being cleaned up. This has been fixed. Note that the solution requires the Hono protocol adapter pods to have
  a service account with an assigned RBAC role that allows to perform get on the pods resource.
• When using Pub/Sub messaging, there were potentially issues concerning the AMQP connection between protocol adapter
  and command router, leading for example to timeouts when MQTT devices subscribed/unsubscribed to the command topic.
  This has been fixed.
• The integration tests now use Apache Kafka 3.5.0 in Raft mode which no longer requires running a separate Apache Zookeeper
  instance and thus simplifies test setup and configuration.
• The command line client was still trying to connect to the insecure ports of the Sandbox. This has been changed so that
  the client now uses the TLS endpoints and requires the user to specify a trust store for validating the server certificate.
• All components now use Quarkus 3.2.9.Final.
• The CoAP adapter now uses Californium 3.10.0.

Deprecations

• According to the MongoDB Software Lifecycle Schedule support
  for MongoDB 4.4 will end Feb 2024.
  Until that date the MongoDB based Device Registry will be tested with MongoDB 4.4, 5.0, 6.0 and 7.0 in the CI workflows.
  However, support for MongoDB 4.4 in Hono has been deprecated and will be removed in a future version altogether.
  Users are encouraged to migrate to MongoDB 6.0 or later.