[no-release-notes] Release v0.56.5

[coffeegoddd]

Created by the Release workflow to update DoltgreSQL's version

[github-actions]

	Main	PR
covering_index_scan_postgres	2088.83/s	2077.34/s	-0.6%
groupby_scan_postgres	129.56/s	126.16/s	-2.7%
index_join_postgres	670.11/s	668.50/s	-0.3%
index_join_scan_postgres	867.00/s	861.10/s	-0.7%
index_scan_postgres	24.69/s	24.64/s	-0.3%
oltp_delete_insert_postgres	878.90/s	888.48/s	+1.0%
oltp_insert	750.18/s	742.51/s	-1.1%
oltp_point_select	3353.38/s	3373.53/s	+0.6%
oltp_read_only	3368.03/s	3370.08/s	0.0%
oltp_read_write	2529.55/s	2521.23/s	-0.4%
oltp_update_index	776.78/s	771.38/s	-0.7%
oltp_update_non_index	837.80/s	826.44/s	-1.4%
oltp_write_only	1839.56/s	1831.72/s	-0.5%
select_random_points	1985.24/s	2006.35/s	+1.0%
select_random_ranges	1144.55/s	1142.51/s	-0.2%
table_scan_postgres	23.30/s	23.24/s	-0.3%
types_delete_insert_postgres	828.41/s	819.77/s	-1.1%
types_table_scan_postgres	8.00/s	8.04/s	+0.4%

[itoqa]

Commit: 4d48068: 4 test cases ran, 0 failed ❌, 4 passed ✅, 0 additional findings ⚠️.

Summary

The run exercised core startup and configuration behavior, confirming the service boots with explicit cluster settings, reports readiness, and accepts normal SQL connections. It also covered release/version consistency paths by checking that version information stays aligned across runtime metadata and validation artifacts, including recovery from an interrupted regeneration flow.

Safe to merge — the tested changes behaved as expected across the main happy paths for startup, connectivity, and version/minimum-version consistency, with no regressions detected. The results indicate low merge risk because the PR’s functional areas were validated and no blocking failures appeared.

Tests run by Ito

Result	Severity	Type	Description
✅	—	Cluster	A valid YAML config with cluster keys loads successfully via --config, the server reaches "Server ready. Accepting connections.", and localhost:5432 accepts SQL connections.
✅	—	Validation	TestMinVersionsValid passed against the committed min-version snapshot with no mismatch diff.
✅	—	Validation	After simulating an interruption between version edits and snapshot regeneration, rerunning the remaining regeneration step restored artifact consistency and the validation test passed.
✅	—	Version	Server startup exposed the expected 0.56.5 version through SQL metadata, consistent with the built binary version output.

Tip

Reply with @itoqa to send us feedback on this test run.

[github-actions]

	Main	PR
Total	42090	42090
Successful	18270	18270
Failures	23820	23820
Partial Successes1	5334	5334

	Main	PR
Successful	43.4070%	43.4070%
Failures	56.5930%	56.5930%

Footnotes

1. These are tests that we're marking as Successful, however they do not match the expected output in some way. This is due to small differences, such as different wording on the error messages, or the column names being incorrect while the data itself is correct. ↩