Skip to content

Release v16.0.5

Choose a tag to compare

@github-actions github-actions released this 14 Jul 07:12
a43476a

Summary

Restores the pre-16.0 ability to run Chronicle without TLS. Since 16.0.0 the main port has been TLS-only, so Tls:Enabled=false — documented for deployments that terminate TLS upstream — crashed on startup instead of serving plaintext, and development could no longer run without a certificate. TLS on a single multiplexed port remains the default.

Added

  • Tls:Enabled=false runs Chronicle in cleartext: h2c gRPC on the main port and the Workbench, REST API, OAuth and health surface on ManagementPort (8080 by default). Use it when TLS is terminated upstream by a load balancer/ingress, or for local development with no certificate.
  • Optional HealthPort exposes the /health endpoint on a dedicated plaintext port for orchestrator and load-balancer probes, while gRPC, the API and OAuth stay on TLS on the main port.

Changed

  • The startup error for a missing production certificate now states that TLS can be disabled with Tls:Enabled=false, rather than only that a certificate is required.

Fixed

  • Tls:Enabled=false no longer crashes the server on startup — it now produces a working plaintext server, matching the property's documentation.

🤖 Generated with Claude Code