Allowed displaying statistics on size of the MT_SPI message components (bytes) sent from the node with the shardman.pg_stat_silk_msg_components view.

Updated the behavior while planning: if a prepared statement connects to a generic plan that cannot be pruned effectively, then another planning and comparison with a custom plan occur.

Updated the supported version of pgpro_pwr to 4.10.

Updated the supported version of pg_proaudit to 2.0.

Updated the etcd client version to 3.6.4.

Updated the shardmanctl status command that now can show status of a cluster in standby mode.

Guaranteed the data consistency when forming user lists.

Added new configuration parameters to work with syncpoints: syncpointInterval that allows specifying how often is a syncpoint created (in seconds), syncpointEnabled that enables monitor that periodically creates syncpoints, and syncpointLimit that specifies the amount of the most recent syncpoints stored.

Added new configuration parameters to work with a standby cluster: intervalWalReceiveCheck, intervalLSNFinder, intervalWalApply, intervalCheckLSN, timeoutApplyLSN, intervalWalSyncArbiter.

Added a feature of a cluster restart with minimum downtime by means of the shardmanctl restart rolling command.

Updated the replication slot configuration that is now configured on a node level of a standby.

Disabled coloring of the log level when executing any shardmanctl command.

Lifted a limitation, now global and sharded tables can be created during a backup process.

Fixed a bug that resulted in panic during the rebalance process.

Fixed an issue that could result in instances restart due to a short connection loss with etcd.

Fixed an issue the the waiting indicator not being displayed.

Fixed the BDU:2025-02344 and GHSA-fv92-fjc5-jj9h vulnerabilities.

Fixed the GO-2025-3770 vulnerability.

Fixed a bug that previously resulted in adding new nodes failure if the shardman schema had global tables with data or global sequences.

Fixed the shardmanctl backup issue, now does not create an invalid backup, as its execution stops on every shard if any error occurs.