Release v2.0.0
Changed
- The client now connects to the Chronicle Kernel over a single port (
35000) instead of a separate gRPC port plus a management HTTP port (8080). The OAuth token endpoint is derived from the connection's own host and port. - TLS is now enabled by default for local development — the Kernel's consolidated port requires TLS to multiplex gRPC and OAuth/API traffic, so the development connection string and
ChronicleOptions.development()no longer disable it. The client automatically trusts the Kernel's auto-generated self-signed development certificate.
Removed
ChronicleConnectionString.managementPort(and its8080default) — no longer needed now that OAuth is served on the same port as gRPC.
Breaking Changes
Any caller that explicitly configured managementPort on ChronicleConnectionString will need to remove that configuration. Callers connecting to localhost:35000 for local development no longer need to pass disableTls=true — TLS is now on by default and the Kernel's self-signed certificate is trusted automatically.