[auto-bump] [no-release-notes] dependency by angelamayxie

[coffeegoddd]

☕ An Automated Dependency Version Bump PR 👑

Initial Changes

The changes contained in this PR were produced by `go get`ing the dependency.

```bash
go get github.com/dolthub/[dependency]/go@[commit]
```

[github-actions]

	Main	PR
Total	42090	42090
Successful	19270	19274
Failures	22820	22816
Partial Successes1	5459	5459

	Main	PR
Successful	45.7828%	45.7923%
Failures	54.2172%	54.2077%

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

copyselect

QUERY: drop table test3;

join

QUERY: select unique2, x.*
from int4_tbl x left join lateral (select unique1, unique2 from tenk1 where f1 = unique1) ss on true;

QUERY: select * from int4_tbl i left join
  lateral (select * from int2_tbl j where i.f1 = j.f1) k on true;

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

[coffeegoddd]

@coffeegoddd DOLT

read_tests	from_latency	to_latency	percent_change
covering_index_scan_postgres	2.48	2.43	-2.02
groupby_scan_postgres	77.19	75.82	-1.77
index_join_postgres	2.22	2.22	0.0
index_join_scan_postgres	1.58	1.58	0.0
index_scan_postgres	467.3	467.3	0.0
oltp_point_select	0.36	0.37	2.78
oltp_read_only	6.32	6.32	0.0
select_random_points	0.7	0.7	0.0
select_random_ranges	1.01	1.01	0.0
table_scan_postgres	467.3	458.96	-1.78
types_table_scan_postgres	1170.65	1170.65	0.0

write_tests	from_latency	to_latency	percent_change
oltp_delete_insert_postgres	6.67	6.67	0.0
oltp_insert	3.36	3.36	0.0
oltp_read_write	13.46	13.22	-1.78
oltp_update_index	3.55	3.55	0.0
oltp_update_non_index	3.25	3.25	0.0
oltp_write_only	7.04	6.91	-1.85
types_delete_insert_postgres	7.17	7.17	0.0

[itoqa]

Commit: 6aa538a: 14 test cases ran, 14 passed ✅.

Summary

Coverage spans core database behavior, including precise handling of boundary and constrained values, transaction and session recovery after errors, persistence across commits and reconnects, versioned data and branch operations, and PostgreSQL client compatibility. It also covers dependency integrity and production build health, representing happy paths, edge cases, error recovery, and integration behavior rather than UI presentation.

Safe to merge — the exercised application and integration behaviors show no PR-attributable regressions or new failures, so there is no merge blocker identified in this run. A few environment-related limitations affect how some checks were executed, but they are not evidence of a defect in this change.

Tests run by Ito

Result	Severity	Type	Description
✅	—	General	The database kept the exact number, date, timestamp, and integer-array values after an update, commit, and fresh connection. It also rejected an invalid foreign-key insert without leaving a partial row.
✅	—	General	The database returned a clear error for the unsupported PREPARE statement, then the same connection updated the row and read back the new value.
✅	—	General	Constrained numeric, array, JSONB, and temporal values were stored and read correctly, and the committed update was visible. A PostgreSQL client also completed the required parameterized prepared query successfully; the earlier error came from testing unsupported SQL PREPARE syntax instead of the client protocol.
✅	—	General	The database kept the first row in the commit and kept the later row as an uncommitted change. Both branches pointed to the same commit, and the clean branch showed only the intended committed row.
✅	—	General	After a duplicate entry failed, rollback cleared the error and the retry was saved. A new connection saw only the valid retry row.
✅	—	Client	The client connected, created and populated a table, committed an update, and successfully ran a parameterized prepared query. The earlier error came from using unsupported SQL PREPARE syntax instead of the client protocol used by this test.
✅	—	Dolt	The table row remained after staging and committing, and the database reported no remaining changes.
✅	—	Query	The supported constrained SQL paths remain implemented, including foreign-key checks, temporary-table lookup, and representative values. A fresh runtime rerun was blocked because the local server and Go toolchain were unavailable.
✅	—	Rev	The three upgraded modules resolve at the requested versions, their checksums verify, and the dependency files contain only the intended update.
✅	—	Rev	The production code compiled successfully with the upgraded engine dependencies, and the resulting Doltgres executable reported its version. The required wrapper could not run in the local environment because Docker was unavailable, but an equivalent container build produced the expected binary.
✅	—	Rev	The core engine test suite passed across all applicable packages after the temporary local credential bypass was removed. SQL authorization and behavior were therefore verified without a production-code defect.
✅	—	Rev	Transaction checks passed for starting work, handling failed statements, retrying changes, saving them, undoing them, and clearing session state.
✅	—	Rev	Commits, branches, merges, and historical reads completed successfully. The version-controlled data returned the expected rows in the local regression suite.
✅	—	Rev	PostgreSQL clients connected successfully, ran prepared and parameterized statements, decoded results, and recovered after errors.

Tip

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

[github-actions]

This PR has been superseded by #3245