Release v2.0.0
Summary
Chronicle's Kernel has consolidated gRPC and OAuth/HTTP traffic onto a single TLS port (default 35000), removing the separate HTTP management port (8080). TLS is now mandatory on that port; in development the Kernel auto-generates a self-signed certificate and the client trusts it automatically. This PR updates the CLI to match, using the same approach as the reference .NET client changes.
Removed
--management-portflag,CHRONICLE_MANAGEMENT_PORTenvironment variable, and themanagement-portcontext key. The OAuth token endpoint is now derived from the connection string's server address instead of a separately configured port.
Changed
- The default connection string no longer disables TLS. The CLI connects over TLS by default and automatically trusts the Chronicle server's self-signed development certificate, so local setups need no manual TLS configuration.
- Bumped
Cratis.Chronicle.Connections,Cratis.Chronicle.Contracts, andCratis.Chronicle.XUnit.Integrationto16.0.1(first release with the single-port client APIs), andTestcontainersto4.13.0to satisfy its new minimum version requirement.
Test plan
-
dotnet build(Cli, Cli.Specs, Integration/Chronicle) — 0 warnings, 0 errors in Release -
dotnet testonCli.Specs— 142/142 passed -
dotnet testonIntegration/Chronicleagainst a locally built single-port Chronicle dev image — 161/161 passed (auth/login, connection errors, and every command group) - Manually ran
cratis get-startedwith no config to verify the onboarding panel renders correctly with the new connection string