Release 2.3.0 Added - When failover mode is stateful, all manual leader promotions will be consistent: every instance before becoming writable performs `wait_lsn` operation to sync with previous one. If consistency couldn't be reached due to replication failure, a user could either revert it (promote previous leader), or force promotion to be inconsistent. - Early logger initialization (for Tarantool > 2.5.0-100, which supports it). - Add `probe_uri_timeout` argparse option responsible for retrying "Can't ping myself" error on startup. - New test helper: `cartridge.test-helpers.etcd`. - Support `on_push` and `on_push_ctx` options for `cartridge.rpc_call()`. - Changing users password invalidates HTTP cookie. - Support GraphQL default variables (https://graphql.org/learn/queries/#default-variables). Fixed - Eventual failover may miss an event while roles are being reconfigured. - Compatibility with pipe logging, see https://github.com/tarantool/tarantool/issues/5220. - Non-informative assertion when instance is bootstrapped with a distinct `advertise_uri`. - Indexing `nil` value in `get_topology()` query. - Initialization race of vshard storage which results in `OperationError`. - Lack of vshard router reconnection attempts to the replicas. - Make GraphQL syntax errors more clear. - Better `errors.pcall()` performance, `errors` rock updated to v2.1.4. Enhanced is WebUI - Show instance names in issues list. - Show app name in window title. - Add "Force leader promotion" button in stateful failover mode. - Indicate consistent switchover problems with a yellow leader flag.