[no-release-notes] Release v1.3.0

[coffeegoddd]

Created by the Release workflow to update DoltgreSQL's version

[github-actions]

	Main	PR
Total	42090	42090
Successful	19245	19246
Failures	22845	22844
Partial Successes1	5469	5469

	Main	PR
Successful	45.7234%	45.7258%
Failures	54.2766%	54.2742%

${\color{lightgreen}Progressions (1)}$

subselect

QUERY: select count(*) from tenk1 t
where (exists(select 1 from tenk1 k where k.unique1 = t.unique2) or ten < 0);

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: a6afcc1: 6 test cases ran, 6 passed ✅.

Summary

Coverage focuses on release-version consistency across fresh startup modes, executable reporting, restart behavior, and continued use of existing data, including reads, writes, commits, and reconnects. The exercised behavior is primarily happy-path startup, compatibility, persistence, and basic regression coverage, with no adversarial or UI-focused scenarios represented.

Safe to merge — all exercised behaviors passed, with no regressions, new failures, or previously flagged failures attributable to this PR. Overall merge risk is low; broader edge-case coverage may be considered separately but is not a blocker here.

Tests run by Ito

Result	Severity	Type	Description
✅	—	General	The server started successfully in memory and on local disk. Both startup modes reported the same release metadata, 1.3.0.
✅	—	General	The server reported release 1.3.0 before and after restarting with the existing data directory. Startup completed normally, with no version mismatch.
✅	—	Release	The running local Doltgres server reports release version 1.3.0 through its release metadata, while the PostgreSQL compatibility version remains 15.5.
✅	—	Rev	The built Doltgres executable exited successfully and reported version 1.3.0.
✅	—	Rev	The upgraded server read two existing rows, accepted a committed write, and returned that write after a separate reconnect.
✅	—	Startup	The in-memory server started successfully, accepted a basic database request, and reported release 1.3.0.

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.52	2.52	0.0
groupby_scan_postgres	74.46	75.82	1.83
index_join_postgres	2.22	2.22	0.0
index_join_scan_postgres	1.58	1.58	0.0
index_scan_postgres	484.44	484.44	0.0
oltp_point_select	0.37	0.36	-2.7
oltp_read_only	6.32	6.43	1.74
select_random_points	0.7	0.7	0.0
select_random_ranges	1.03	1.01	-1.94
table_scan_postgres	484.44	475.79	-1.79
types_table_scan_postgres	1213.57	1213.57	0.0

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.22	13.46	1.82
oltp_update_index	3.55	3.55	0.0
oltp_update_non_index	3.25	3.25	0.0
oltp_write_only	6.91	7.04	1.88
types_delete_insert_postgres	7.17	7.17	0.0