chore(deps): bump the all group with 2 updates

[dependabot]

Bumps the all group with 2 updates: github.com/ydb-platform/ydb-go-sdk/v3 and modernc.org/sqlite.

Updates github.com/ydb-platform/ydb-go-sdk/v3 from 3.135.14 to 3.136.2

Release notes

Sourced from github.com/ydb-platform/ydb-go-sdk/v3's releases.

v3.136.2

• Fixed MultiWriterWithTransaction.Write to materialize lazy query transactions via tx.UnLazy before writing (same as single-partition transactional writer)
• Fixed MultiWriterWithTransaction: pass transaction to each incoming message

Full Changelog: v3.136.1...v3.136.2

v3.136.1

• Changed the retry behavior for operation error TIMEOUT from non-retryable to conditionally retryable
• Added public retry.TypeInstant enum alias to retry.TypeNoBackoff

Full Changelog: v3.136.0...v3.136.1

v3.136.0

• The query.WithResponsePartPrefetch(n) method has been added to enable the prefetching of parts of query results. By default, this feature is disabled. Prefetching produces the following effects:
  • One additional goroutine per query.
  • Approximately 5 allocations per query.
  • Approximately 200–300 additional bytes per query. However, each query also reduced the execution time by approximately 2 milliseconds.

Full Changelog: v3.135.15...v3.136.0

v3.135.15

• database/sql driver (no public API changes): QueryContext / Stmt.QueryContext / Tx.QueryContext cancellation propagated through row iteration consistently—the SQL Rows adapter retained that context for every Next, NextResultSet, and column-metadata call, and both Query Service and Table Service backends received it where supported.
• When using QueryService (ydb.WithQueryService(true), default), canceling the query context after starting to read a result set surfaced context.Canceled from (*sql.Rows).Err() after Next stopped, matching typical database/sql expectations for context-aware queries.
• When using TableService (ydb.WithQueryService(false)), row iteration continued to rely on the table client read path; Rows.Err() after cancel could be empty or io.EOF once rows were exhausted, rather than the cancellation error.
• Replaced internal query-client "done" signal channels with atomic.Bool to improve performance:
  • Reduced allocations per query and decreased latency for each query.
  • Disabled cascading cancellation of all child operations, such as canceling a query on session close or query-client close — YDB server is supposed to cancel query executions on closing sessions.

Full Changelog: v3.135.14...v3.135.15

Changelog

Sourced from github.com/ydb-platform/ydb-go-sdk/v3's changelog.

v3.136.2

• Fixed MultiWriterWithTransaction.Write to materialize lazy query transactions via tx.UnLazy before writing (same as single-partition transactional writer)
• Fixed MultiWriterWithTransaction: pass transaction to each incoming message

v3.136.1

• Changed the retry behavior for operation error TIMEOUT from non-retryable to conditionally retryable
• Added public retry.TypeInstant enum alias to retry.TypeNoBackoff

v3.136.0

• The query.WithResponsePartPrefetch(n) method has been added to enable the prefetching of parts of query results. By default, this feature is disabled. Prefetching produces the following effects:
  • One additional goroutine per query.
  • Approximately 5 allocations per query.
  • Approximately 200–300 additional bytes per query. However, each query also reduced the execution time by approximately 2 milliseconds.

v3.135.15

• database/sql driver (no public API changes): QueryContext / Stmt.QueryContext / Tx.QueryContext cancellation propagated through row iteration consistently—the SQL Rows adapter retained that context for every Next, NextResultSet, and column-metadata call, and both Query Service and Table Service backends received it where supported.
• When using QueryService (ydb.WithQueryService(true), default), canceling the query context after starting to read a result set surfaced context.Canceled from (*sql.Rows).Err() after Next stopped, matching typical database/sql expectations for context-aware queries.
• When using TableService (ydb.WithQueryService(false)), row iteration continued to rely on the table client read path; Rows.Err() after cancel could be empty or io.EOF once rows were exhausted, rather than the cancellation error.
• Replaced internal query-client "done" signal channels with atomic.Bool to improve performance:
  • Reduced allocations per query and decreased latency for each query.
  • Disabled cascading cancellation of all child operations, such as canceling a query on session close or query-client close — YDB server is supposed to cancel query executions on closing sessions.

Commits

• 9e71dce Release v3.136.2
• bd86954 LOGBROKER-10206 Pass tx to incoming messages (#2154)
• 8147e30 Release v3.136.1
• 20ae4ec Changed the retry behavior for operation error TIMEOUT from NonRetryable ...
• bcbfbbc Release v3.136.0
• 3455d18 perf: prefetch N parts of QueryClient response stream for decrease query late...
• 0cc9711 Release v3.135.15
• be40ba3 refactoring for better perf: replaced done signal channels to atomic.Bool, ...
• 927c45b Table/Query/DatabaseSQL benchmarks (#2147)
• See full diff in compare view

Updates modernc.org/sqlite from 1.50.0 to 1.50.1

Changelog

Sourced from modernc.org/sqlite's changelog.

Changelog

• 2026-05-10 v1.50.1:

  • Upgrade to SQLite 3.53.1.

• 2026-04-24 v1.50.0:

  • Upgrade to sqlite-vec v0.1.9.
  • Introduce ColumnInfo, enabling dynamic query builders and ORMs to retrieve underlying SQLite C-API metadata (OriginName, TableName, DatabaseName, and DeclType).
  • This feature is exposed via the idiomatic database/sql escape hatch (*sql.Conn).Raw(), avoiding custom statement handles and keeping the standard library workflow intact.
  • See [GitLab merge request #113](https://gitlab.com/cznic/sqlite/-/merge_requests/113), thanks Josh Bleecher Snyder!

• 2026-04-17 v1.49.0: Upgrade to SQLite 3.53.0.

  • Added -DSQLITE_ENABLE_DBPAGE_VTAB to the transpilation. See "The SQLITE_DBPAGE Virtual Table" for details.

• 2026-04-06 v1.48.2:

  • Fix ABI mapping mismatch in the pre-update hook trampoline that caused silent truncation of large 64-bit RowIDs.
  • Ensure the Go trampoline signature correctly aligns with the public sqlite3_preupdate_hook C API, preventing data corruption for high-entropy keys (e.g., Snowflake IDs).
  • See [GitLab merge request #98](https://gitlab.com/cznic/sqlite/-/merge_requests/98), thanks Josh Bleecher Snyder!
  • Fix the memory allocator used in (*conn).Deserialize.
  • Replace tls.Alloc with sqlite3_malloc64 to prevent internal allocator corruption. This ensures the buffer is safely owned by SQLite, which may resize or free it due to the SQLITE_DESERIALIZE_RESIZEABLE and SQLITE_DESERIALIZE_FREEONCLOSE flags.
  • Prevent a memory leak by properly freeing the allocated buffer if fetching the main database name fails before handing ownership to SQLite.
  • See [GitLab merge request #100](https://gitlab.com/cznic/sqlite/-/merge_requests/100), thanks Josh Bleecher Snyder!
  • Fix (*conn).Deserialize to explicitly reject nil or empty byte slices.
  • Prevent silent database disconnection and connection pool corruption caused by SQLite's default behavior when sqlite3_deserialize receives a 0-length buffer.
  • See [GitLab merge request #101](https://gitlab.com/cznic/sqlite/-/merge_requests/101), thanks Josh Bleecher Snyder!
  • Fix commitHookTrampoline and rollbackHookTrampoline signatures by removing the unused pCsr parameter.
  • Aligns internal hook callbacks accurately with the underlying SQLite C API, cleaning up the code to prevent potential future confusion or bugs.
  • See [GitLab merge request #102](https://gitlab.com/cznic/sqlite/-/merge_requests/102), thanks Josh Bleecher Snyder!
  • Fix checkptr instrumentation failures during go test -race when registering and using virtual tables (vtab).
  • Allocate sqlite3_module instances using the C allocator (libc.Xcalloc) instead of the Go heap. This ensures transpiled C code can safely perform pointer operations on the struct without tripping Go's pointer checks.
  • See [GitLab merge request #103](https://gitlab.com/cznic/sqlite/-/merge_requests/103), thanks Josh Bleecher Snyder!
  • Fix data race on mutex.id in the mutexTry non-recursive path.
  • Ensure consistent atomic writes (atomic.StoreInt32) to prevent data races with atomic loads in mutexHeld and mutexNotheld during concurrent execution.
  • See [GitLab merge request #104](https://gitlab.com/cznic/sqlite/-/merge_requests/104), thanks Josh Bleecher Snyder!
  • Fix resource leak in (*Backup).Commit where the destination connection was not closed on error.
  • Ensure dstConn is properly closed when sqlite3_backup_finish fails, preventing file descriptor, TLS, and memory leaks.
  • See [GitLab merge request #105](https://gitlab.com/cznic/sqlite/-/merge_requests/105), thanks Josh Bleecher Snyder!
  • Fix Exec to fully drain rows when encountering SQLITE_ROW, preventing silent data loss in DML statements.
  • Previously, Exec aborted after the first row, meaning INSERT, UPDATE, or DELETE statements with a RETURNING clause would fail to process subsequent rows. The execution path now correctly loops until SQLITE_DONE and properly respects context cancellations during the drain loop, fully aligning with native C sqlite3_exec semantics.
  • See [GitLab merge request #106](https://gitlab.com/cznic/sqlite/-/merge_requests/106), thanks Josh Bleecher Snyder!
  • Fix "Shadowed err value (stmt.go)".
  • See [GitLab issue #249](https://gitlab.com/cznic/sqlite/-/work_items/249), thanks Emrecan BATI!
  • Fix silent omission of virtual table savepoint callbacks by correctly setting the sqlite3_module version.
  • See [GitLab merge request #107](https://gitlab.com/cznic/sqlite/-/merge_requests/107), thanks Josh Bleecher Snyder!
  • Fix vfsRead to properly handle partial and fragmented reads from io.Reader.
  • Replace f.Read with io.ReadFull to ensure the buffer is fully populated, preventing premature SQLITE_IOERR_SHORT_READ errors on valid mid-stream partial reads. Unread tail bytes at EOF are now efficiently zero-filled using the built-in clear function.
  • See [GitLab merge request #108](https://gitlab.com/cznic/sqlite/-/merge_requests/108), thanks Josh Bleecher Snyder!
  • Refactor internal error formatting to safely handle uninitialized or closed database pointers.
  • Prevent a misleading "out of memory" error message when an operation fails and the underlying SQLite database handle is NULL (db == 0).
  • See [GitLab merge request #109](https://gitlab.com/cznic/sqlite/-/merge_requests/109), thanks Josh Bleecher Snyder!

... (truncated)

Commits

• b95ed45 upgrade to SQLite 3.53.1
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions