Version changed to 0.2.4

Author: percona-ysorokin

README.md

@@ -175,7 +175,7 @@ For instance,
 ```
 may print
 ```
-0.2.3
+0.2.4
 ```
 
 #### 'search_by_timestamp' operation mode

packaging/debian/changelog

@@ -1,3 +1,12 @@
+percona-binlog-server (0.2.4-1) unstable; urgency=low
+
+  * PS-11137 binlog-server fails to reconnect in position-based replication mode when network timeout interrupts a transaction.
+  * PS-11136 non-GTID transactions cause one storage flush per transaction, bypassing size/interval checkpointing.
+  * PS-11080 Spoiled logical clock information in rewritten binlog.
+  * PS-11205 When fs_buffer_directory is not set the temporary buffer directory is created in the current binary path rather than in /tmp.
+
+ -- Yura Sorokin <yura.sorokin@percona.com>  Wed, 03 Jun 2026 11:59:40 +0200
+
 percona-binlog-server (0.2.3-1) unstable; urgency=low
 
   * PS-11033 Crash when S3 bucket accumulates large number of objects; recovery requires manual intervention.

packaging/debian/rules

@@ -9,7 +9,7 @@ export DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
 export CODENAME := $(shell . /etc/os-release && echo $$VERSION_CODENAME)
 
 # Versions
-export DEB_VERSION=0.2.3
+export DEB_VERSION=0.2.4
 export BOOST_VERSION=1.88.0
 export AWS_VERSION=1.11.570
 

packaging/rpm/binlog-server.spec

@@ -134,6 +134,12 @@ install -D -m 0644  main_config.json %{buildroot}/%{_sysconfdir}/percona-binlog-
 
 
 %changelog
+* Wed Jun 03 2026 Yura Sorokin <yura.sorokin@percona.com> - 0.2.4-1
+- PS-11137 binlog-server fails to reconnect in position-based replication mode when network timeout interrupts a transaction.
+- PS-11136 non-GTID transactions cause one storage flush per transaction, bypassing size/interval checkpointing.
+- PS-11080 Spoiled logical clock information in rewritten binlog.
+- PS-11205 When fs_buffer_directory is not set the temporary buffer directory is created in the current binary path rather than in /tmp.
+
 * Fri Apr 24 2026 Yura Sorokin <yura.sorokin@percona.com> - 0.2.3-1
 - PS-11033 Crash when S3 bucket accumulates large number of objects; recovery requires manual intervention.