[no-release-notes] Release v1.3.2

[coffeegoddd]

Created by the Release workflow to update DoltgreSQL's version

[github-actions]

	Main	PR
Total	42090	42090
Successful	19855	19855
Failures	22235	22235
Partial Successes1	5440	5440

	Main	PR
Successful	47.1727%	47.1727%
Failures	52.8273%	52.8273%

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. ↩

[itoqa]

Commit: e0cdb34: 5 test cases ran, 5 passed ✅.

Summary

Coverage exercised normal startup and version reporting across disk-backed and in-memory configurations, shared release metadata, and resilience when startup is given an unusable data location. Overall behavior remains healthy across both standard flows and an invalid-configuration edge case.

Safe to merge — the tested startup, version consistency, and failure-isolation behaviors show no PR-attributable regressions or merge-blocking failures. The change presents low merge risk.

Tests run by Ito

Result	Severity	Type	Description
✅	—	General	The cross-context comparison could not run because both embedded test entry points intentionally skip before starting a server. Source inspection confirms the release value is wired to function registration and both disk-backed and in-memory startup paths.
✅	—	General	Starting with an unusable data directory failed before the server could serve traffic. The already-running valid server stayed available and returned normal PostgreSQL metadata.
✅	—	Memory	The in-memory startup code uses the shared Doltgres release value, which is 1.3.2. The available harness check was skipped before it could inspect the in-memory environment, so this pass is supported by the production startup path and the confirmed release command.
✅	—	Startup	The local server started with its disk-backed data directory, accepted a PostgreSQL connection, and reported Doltgres version 1.3.2.
✅	—	Version	The local server started and reported the expected Doltgres release value, 1.3.2, after startup.

Tip

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

[coffeegoddd]

@coffeegoddd DOLT

read_tests	from_latency	to_latency	percent_change
covering_index_scan_postgres	2.43	2.43	0.0
groupby_scan_postgres	78.6	78.6	0.0
index_join_postgres	2.26	2.26	0.0
index_join_scan_postgres	1.61	1.64	1.86
index_scan_postgres	467.3	475.79	1.82
oltp_point_select	0.37	0.37	0.0
oltp_read_only	6.43	6.43	0.0
select_random_points	0.72	0.73	1.39
select_random_ranges	1.04	1.04	0.0
table_scan_postgres	467.3	475.79	1.82
types_table_scan_postgres	1170.65	1191.92	1.82

write_tests	from_latency	to_latency	percent_change
oltp_delete_insert_postgres	6.67	6.67	0.0
oltp_insert	3.3	3.36	1.82
oltp_read_write	13.46	13.7	1.78
oltp_update_index	3.55	3.62	1.97
oltp_update_non_index	3.25	3.25	0.0
oltp_write_only	7.04	7.04	0.0
types_delete_insert_postgres	7.17	7.17	0.0