Release v16.0.0

Summary

Chronicle Server now consolidates all traffic onto a single port (35000) instead of exposing a separate management port. Because a single port can only serve both gRPC (HTTP/2) and HTTP/1.1 by negotiating the protocol per connection over TLS, the port now always uses TLS — with a self-signed certificate generated automatically in development so it still works with zero setup.

Changed

• Chronicle Server serves gRPC (HTTP/2) together with the Workbench, REST API, OAuth flows and health checks (HTTP/1.1) on the single port 35000, multiplexed over TLS. The Workbench is now reached at https://localhost:35000. (#3372)
• The Chronicle port now always uses TLS. In development a self-signed certificate is generated automatically when none is configured, and clients accept it without any setup; a certificate is required in production. (#3372)

Removed

• The managementPort server configuration option and the client ManagementPort option — all traffic uses the single port. (#3372)
• The separate Workbench TLS configuration (workbench.tls); the single port uses the top-level tls certificate. (#3372)
• The Aspire ChronicleResource management endpoint (DefaultManagementPort and the management endpoint); a single grpc endpoint now serves everything. (#3372)

🤖 Generated with Claude Code