This is an automated email from the ASF dual-hosted git repository.

frankgh pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-sidecar.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 0f7180d1 Preparing build for the 0.3.0 release (#322)
0f7180d1 is described below

commit 0f7180d104d1e6b9564b02edbe12633ec307bcfc
Author: Francisco Guerrero <[email protected]>
AuthorDate: Wed Feb 18 13:01:54 2026 -0800

    Preparing build for the 0.3.0 release (#322)
---
 NEWS.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/NEWS.txt b/NEWS.txt
index 390ecf54..36c183b0 100644
--- a/NEWS.txt
+++ b/NEWS.txt
@@ -6,6 +6,16 @@ New features
     - ProcessLifecycleProvider for managing Cassandra process lifecycle 
(start/stop) via sidecar APIs with configurable
       startup and shutdown commands, state tracking, and support for custom 
environment configurations. Usage example
       available on examples/lifecycle.
+    - CDC (Change Data Capture) support with CDC Publisher implementation, 
CDC/Kafka configuration APIs, and automatic
+      cleanup of commit log segments in the cdc_raw directory.
+    - Node management operations including on-demand repair, compaction 
management (stop/statistics), node drain,
+      and move node to new token.
+    - Stateless JWT authentication using public keys with authentication and 
authorization caching for improved
+      performance, and endpoint to invalidate auth caches.
+    - Schema monitoring with CassandraClusterSchemaMonitor implementation for 
tracking schema changes across the cluster.
+    - Live Migration enhancements including status persistence endpoint for 
migration safety and tracking.
+    - Additional operational endpoints for system disk information, Cassandra 
settings (from system_views.settings),
+      and compaction statistics.
 
 0.2
 ===


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to