chore: bump the compatible-go-dependencies group across 1 directory with 8 updates

[dependabot]

Bumps the compatible-go-dependencies group with 8 updates in the / directory:

Package	From	To
modernc.org/sqlite	1.58.0	1.59.0
github.com/nats-io/nats.go	1.53.1	1.54.0
github.com/rabbitmq/amqp091-go	1.14.0	1.15.0
github.com/aws/aws-sdk-go-v2	1.46.0	1.47.1
github.com/aws/aws-sdk-go-v2/config	1.33.3	1.33.6
github.com/aws/aws-sdk-go-v2/credentials	1.20.3	1.20.6
github.com/aws/aws-sdk-go-v2/service/sqs	1.51.0	1.52.1
github.com/jackc/pgx/v5	5.10.0	5.11.0

Updates modernc.org/sqlite from 1.58.0 to 1.59.0

Changelog

Sourced from modernc.org/sqlite's changelog.

Changelog

Entries for v1.38.1 through v1.44.1 and for v1.49.1 were added on 2026-09-05, reconstructed from the git history and the merge requests they cite; they were missing at release time.

• 2026-09-15 v1.59.1:

  • make vendor now writes vendor.json: the modernc.org/libsqlite3 and modernc.org/libsqlite_vec commits and the Go toolchain lib/ and vec/ were vendored with, so git show vX.Y.Z:vendor.json says which revisions a release carries. It refuses a dirty sibling checkout, siblings on different modernc.org/libc versions, or a libsqlite_vec built against another libsqlite3. The suite fails when lib/, vec/ or the libc in go.mod no longer match the stamp, so a libc bump goes in the same push as make vendor. Tooling only; the vendored code is unchanged. See [GitLab merge request #140](https://gitlab.com/cznic/sqlite/-/merge_requests/140).
  • vfs.FS.Close now refuses while a database opened through it is still open, returning an error that wraps the new vfs.ErrInUse and leaving the VFS registered. It used to free the VFS the open connection still called through, so the next query crashed the process or read through freed memory. Close the databases first, then the FS.
  • Fix handle reuse in modernc.org/sqlite/vfs on 32-bit targets: after 2^32 file opens in one process the handle counter wrapped and could overwrite a live entry, such as a file system registered at start-up, and crash. 64-bit targets were not affected.
  • The pluggable page cache now panics when a Cache breaks its contract by returning nil, or a different Page, from Fetch for a page SQLite still holds pinned. It used to free memory SQLite was still using, corrupting the database without an error. Only a Cache implementation with that bug is affected; modernc.org/sqlite/pcache is not.
  • Document three limits of the pluggable page cache: a program importing modernc.org/sqlite/vec cannot call RegisterPageCache (it fails with SQLITE_MISUSE), PageCache.Create may be called concurrently, and under cache=shared a Cache is called from several goroutines, serialized by SQLite, so it wants a mutex of its own to run clean under -race. Documentation only.
  • Document two properties of connections in the package documentation: state set on a pooled connection -- PRAGMAs set with Exec, ATTACHed databases, temporary tables, anything registered through sql.Conn.Raw -- is inherited by the next caller to borrow it, and a driver connection reached through Raw is not safe for concurrent use even though every connection is opened SQLITE_OPEN_FULLMUTEX. Documentation only.
  • Add StrictPragmas, opt-in and off by default: once enabled, a connection whose _pragma DSN value holds more than one SQL statement fails to open with ErrMultiStatementPragma, before any DSN parameter is applied. A _pragma value runs as SQL text, so _pragma=foreign_keys(1);ATTACH 'x.db' AS x also attaches, and creates, x.db; the Driver.Open documentation said "a PRAGMA statement" and now says what actually happens. Enabling it is recommended for any application whose DSN is not a compile-time constant.
  • Document SQLite's own URI query parameters on Driver.Open: mode, cache, immutable, nolock, psow and modeof. Every connection is opened with SQLITE_OPEN_URI, so in a DSN starting with file: these have always worked; only the driver's own keys were listed. The docstring also spells out the trap that a plain file name has its query stripped before SQLite sees it, so /path/to.db?mode=ro opens read-write. Documentation only.
  • Resolves [GitLab issue #257](https://gitlab.com/cznic/sqlite/-/issues/257).
  • Add IRP.md, an incident response plan: who runs a response when there are two maintainers in different time zones, how a report is scoped across the three layers this module is built from, the fix path for each, and what to do when a released version is itself the problem -- a published Go module version cannot be recalled, so retract plus a new release is the remedy. Linked from SECURITY.md. Documentation only.
  • Add CONTRIBUTING.md: where to send a merge request, which files are generated and must not be edited by hand, how to build and test across the 20 supported targets, and the AUTHORS/CONTRIBUTORS convention. Contribution guidance previously existed only in GOVERNANCE.md and HACKING.md, neither of which a first-time contributor is likely to open. Documentation only.
  • Add SECURITY.md: report a vulnerability through GitHub private vulnerability reporting, a confidential GitLab issue, or the project's Service Desk address, never a public issue. It states what is in scope -- including transpilation faults, where the generated Go does not faithfully implement the C it came from -- that only the latest release is supported, and that a confirmed report is disclosed through a GitHub advisory, an entry in the Go vulnerability database so govulncheck reports it, and a release note. Documentation only.
  • Ship a Software Bill of Materials: sbom.cdx.json (CycloneDX 1.6) and sbom.spdx.json (SPDX 2.3), both validated against the published schemas, with SBOM.md explaining what they cover. They name what an SBOM built from the module graph cannot see -- the transpiled SQLite 3.53.4 and sqlite-vec C, and the upstreams modernc.org/libc vendors, musl among them -- and mark every component as linked into your binary, test-only, or compiled into nothing. Documentation only.
  • Ship LICENSE-3RD-PARTY.md, a transitively flattened inventory of every third-party component this module carries: the whole Go module graph, the transpiled SQLite and sqlite-vec C that no go.mod names, and the upstreams modernc.org/libc carries in turn, musl among them. It reproduces all seventeen distinct license texts in full and separates what is linked into your binary from what only appears in the module graph. The LICENSE name prefix is what makes go mod vendor carry it into downstream vendor/ trees. Documentation only.

• 2026-09-15 v1.59.0:

  • Bump the pinned modernc.org/libc to v1.75.7 and re-vendor lib/ and vec/. The transpiled SQLite is unchanged, still 3.53.4. On the Linux targets the new libc replaces transpiled musl memcpy, memmove, memset, memcmp and strlen with native Go, cutting CPU time on query-heavy workloads by up to a third; see the new Performance section below. As always, downstream go.mod files must pin the same modernc.org/libc version this repository's go.mod does; see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
  • Hand user-defined function and aggregate callbacks a pooled *FunctionContext instead of allocating a fresh one per call, removing the last driver-side allocation per invocation. Like the argument slice, it is valid only for the duration of the callback and must not be retained past its return. Updates [GitLab issue #226](https://gitlab.com/cznic/sqlite/-/issues/226). See [GitLab merge request #137](https://gitlab.com/cznic/sqlite/-/merge_requests/137).
  • Add regression tests pinning the identity and the pooling of that context. See [GitLab merge request #138](https://gitlab.com/cznic/sqlite/-/merge_requests/138), thanks Ian Chechin!
  • Add a Performance section to the package documentation: measured CPU-time ratios of this driver against the same SQLite compiled from C, where the gap comes from, and the two consequences for applications — index the columns that ORDER BY, GROUP BY and WHERE use, and bound the database/sql pool with SetMaxOpenConns.

• 2026-09-01 v1.58.0:

  • Upgrade to SQLite 3.53.4. It carries upstream's own fix for the journal-rollback data-corruption bug, so the local super-journal patch v1.56.0 introduced is dropped; recovery behavior is unchanged. Also bumps the pinned modernc.org/libc to v1.75.6; as always, downstream modules must pin the same version this one does, see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
  • Add opt-in support for Linux Open File Description (OFD) locks on database files, off by default; without opting in, locking behavior is byte-for-byte that of previous releases. A POSIX record lock is owned by the (process, inode) pair, so any Close of any descriptor of the database file anywhere in the process silently strips SQLite's locks; OFD locks survive that. Enable it process-wide with MODERNC_SQLITE_OFD_LOCK=1 in the environment, or with the new OFDLocking(true) before the first connection is opened; OFDLockingEnabled reports the mode in effect, and the new ErrOFDLockingTooLate and ErrOFDLockingUnavailable report a switch attempted too late and a platform or filesystem without the feature. Why it is process-wide rather than a DSN parameter, what WAL's -shm coordination still uses, and the /proc/locks measurements behind the design are in [GitLab issue #255](https://gitlab.com/cznic/sqlite/-/issues/255).
  • Resolves [GitLab issue #255](https://gitlab.com/cznic/sqlite/-/issues/255). See [GitLab merge request #136](https://gitlab.com/cznic/sqlite/-/merge_requests/136), thanks Nathan Herring (@​technosloth), and thanks Gani Georgiev (@​ganigeorgiev) for pressing the opt-in default!

• 2026-08-19 v1.57.0:

  • Add an opt-in _defensive DSN query parameter turning on SQLite's defensive mode for the connection. On such a connection PRAGMA writable_schema=ON, PRAGMA journal_mode=OFF and PRAGMA schema_version=N become silent no-ops, and writes to a virtual table's shadow tables and to sqlite_dbpage fail. It is a hardening measure, not a sandbox for hostile database files, for which it is only one of the steps SQLite recommends, and it is a property of the connection, not of the file. Absent, or _defensive=0, nothing changes.
  • Reject _defensive=1 together with _journal_mode=OFF (or _journal=OFF) instead of opening a connection in which neither was honoured: SQLite turns that PRAGMA into a no-op that still reports success. Only DSNs using the new parameter can be affected. See [GitHub pull request #6](modernc-org/sqlite#6), thanks wsman!
  • Ship the sqlite-vec license notice this module has been missing since vec/ arrived in v1.47.0. sqlite-vec is Copyright (c) 2024 Alex Garcia, dual-licensed Apache-2.0 OR MIT and used here under MIT; the text now ships as LICENSE-SQLITE_VEC, and make vendor fails rather than quietly dropping it.
  • The SQLite notice is renamed from SQLITE-LICENSE to LICENSE-SQLITE; update any direct links to it. Its contents are unchanged. The rename is what makes go mod vendor carry both notices into downstream vendor/ trees: it selects license files by name prefix, so a name merely ending in LICENSE was never propagated.
  • Let a caller-constructed Driver register its own functions, collations and virtual table modules, through new RegisterFunction, RegisterScalarFunction, RegisterDeterministicScalarFunction, RegisterCollationUtf8 and RegisterModule methods plus Must* variants, and let vtab.RegisterModule honour its db argument. Behavior change: vtab.RegisterModule(db, ...) where db was opened on a caller-constructed Driver used to discard db and land on the registered sqlite driver, reaching every connection in the process; it now lands on that Driver alone, so a sql.Open("sqlite") connection that used to resolve such a module gets no such module. Everything else is additive, and the isolating change discussed in [GitLab issue #254](https://gitlab.com/cznic/sqlite/-/issues/254) is deliberately not made here. See [GitLab merge request #135](https://gitlab.com/cznic/sqlite/-/merge_requests/135), thanks Ian Chechin!
  • Promote freebsd/386, freebsd/arm and netbsd/amd64 from experimental to fully supported. The package documentation's platform table had carried seventeen entries while this module shipped, cross-built and tested twenty; all three have been in the builder matrix since v1.53.0 and pass the full suite on this release's commit. Documentation only — lib/ is byte-for-byte what v1.56.0 shipped.

• 2026-08-03 v1.56.0:

  • Re-vendor the transpiled sources, picking up modernc.org/libsqlite3's patch for an upstream data-corruption bug in SQLite 3.53.3's journal rollback. A crash during the commit of a multi-database (ATTACH) transaction can leave a hot journal whose zeroed super-journal name still validates, so pager_playback() deletes it without playing it back and leaves the database corrupted. Not a transpilation artifact: a plain gcc build of stock 3.53.3 fails on the same bytes. The SQLite version is unchanged at 3.53.3, every supported target carries the patch, and it will be dropped once upstream ships its own fix.
  • Two targets change beyond that patch. linux/s390x now allocates C bit-fields MSB-first as the big-endian ABI requires, from modernc.org/cc/v4 v4.29.1. linux/riscv64 was regenerated on a host running GCC 11.4.0 rather than 13.3.0, which drops some unreferenced compiler-predefined macro constants and changes what PRAGMA compile_options reports; no SQLite code generation differs. Every other target is byte-identical to v1.55.0 apart from the patch above.
  • Bump the pinned modernc.org/libc to v1.74.4 and the remaining dependencies to their current releases. v1.74.2 and v1.74.3 are retracted upstream over a freeaddrinfo lock leak that deadlocks name resolution, and v1.74.4 is the fix. As always, downstream modules must pin the same modernc.org/libc version this one does, see [GitLab issue #177](https://gitlab.com/cznic/sqlite/-/issues/177).
  • Add NewConnector, returning a database/sql/driver.Connector for use with sql.OpenDB. It opens the same connections sql.Open("sqlite", dsn) does, from the same registered driver, so every function, collation, connection hook and virtual table module registered through this package applies to them. It exists for callers that need to interpose on the physical connections database/sql opens — tracing, metrics, connection-scoped setup — for which the alternative was sql.Register, which is process-global, panics on a repeated name and cannot be undone. A runnable sample is in examples/connector. Resolves [GitLab issue #253](https://gitlab.com/cznic/sqlite/-/issues/253), thanks Alessandro Segala (@​ItalyPaleAle)!
  • Documentation sweep. openbsd/amd64 and openbsd/arm64 join the supported platforms table, the vfs DSN query parameter is documented alongside the others on Driver.Open, the stale go generate and GO_GENERATE instructions are replaced by modernc.org/libsqlite3 and make vendor, and vec and vfs gained the package doc comments they were missing. A caller-constructed sqlite.Driver is now documented as not being the driver this package registers as "sqlite": it carries none of the package-level functions and collations, so it can evaluate upper(x) or date(x) differently. Documentation only.

• 2026-07-20 v1.55.0:

  • Add github.com/mattn/go-sqlite3-compatible shorthand DSN query parameters to ease migration from that driver: _busy_timeout/_timeout, _foreign_keys/_fk, _journal_mode/_journal, _synchronous/_sync, _auto_vacuum/_vacuum and _query_only, each setting the correspondingly named PRAGMA. Values are validated against the same set mattn/go-sqlite3 accepts and an unrecognized one fails the connection, so a typo cannot silently downgrade durability. Review DSNs carried over from that driver before upgrading: a key prior releases ignored entirely now takes effect, so _foreign_keys=on begins enforcing constraints and _journal_mode=wal persistently converts the file; and a duration-style _busy_timeout=5s now fails an open that previously succeeded. See [GitLab merge request #134](https://gitlab.com/cznic/sqlite/-/merge_requests/134), thanks Toni Spets (@​beeper-hifi) and Ian Chechin!
  • Validate every DSN query parameter before applying any of them. Parameters were checked as each was reached, so a DSN rejected for a later parameter had already executed the PRAGMAs ahead of it: file:x.db?_journal_mode=wal&_synchronous=bogus failed the connection and yet left x.db converted to WAL. A failed Open now leaves the database as it found it. The accepted values are unchanged. _pragma remains the sole exception, since its values are executed verbatim and can only be rejected by SQLite as they run.

• 2026-07-15 v1.54.0:

... (truncated)

Commits

• c96a4e6 CHANGELOG.md: document the libc v1.75.7 bump and the Performance section
• 35c446e update dependencies, make vendor
• 9ad02ac Merge branch 'udf-context-tests' into 'master'
• d6d84a9 sqlite: pin the identity and the pooling of the FunctionContext in tests
• 59ec397 doc.go: add a Performance section with measured driver-vs-C ratios
• 51cbcbf Merge branch 'udf-call-pool' into 'master'
• e390a0c sqlite: pool the FunctionContext handed to UDF and aggregate callbacks
• 38af581 doc.go, README.md: point readers at CHANGELOG.md
• 37e55e4 CHANGELOG.md: reconstruct the missing entries for v1.38.1 through v1.44.1 and...
• 2f7234f AUTHORS, CONTRIBUTORS: add Nathan Herring; CHANGELOG.md: credit him by name
• See full diff in compare view

Updates github.com/nats-io/nats.go from 1.53.1 to 1.54.0

Release notes

Sourced from github.com/nats-io/nats.go's releases.

Release v1.54.0

Changelog

This release raises the minimum supported Go version to 1.26 and adds support for nats-server v2.15 stream and consumer info fields.

ADDED

• Core NATS:
  • nats.MultipathTCP() option to enable or disable MPTCP for outbound connections (#2145)
  • Conn.ConnectedDomain() to read the JetStream domain advertised by the connected server (#2139)
• JetStream:
  • ClusterInfo.Desired, PeerInfo.Peer, PeerInfo.Pending and StreamSourceInfo.Seq in stream and consumer info, reported by nats-server v2.15 (#2144)
  • Nats-Schedule-Rollup header const and WithScheduleRollup() publish option (#2142)

FIXED

• Core NATS:
  • Panic in DecodeHeadersMsg on inline status tokens shorter than 3 characters. Thanks @​nikitha-m for the contribution (#2101)
  • Data race on Subscription.sid between applyNewSID and removeSub (#2122)
• JetStream:
  • Messages() iterator going silent after a reconnect that completes between Next() calls. Thanks @​1995parham for the contribution (#2135)
  • Legacy ordered consumer silently losing messages when the subscription hits its pending limits (#2137)
  • Legacy ordered consumer reset resurrecting an unsubscribed or draining subscription (#2133)

IMPROVED

• Core NATS:
  • Avoid allocation when parsing header message arguments with a fifth token. Thanks @​0xAozora for the contribution (#2130)
  • Preallocate reply subject buffers. Thanks @​0xAozora for the contribution (#2123)
• JetStream:
  • Prevent doErr closure escaping to the heap in async publish reply handling. Thanks @​0xAozora for the contribution (#2127)
  • Fix typo in Publisher interface methods comment. Thanks @​sreeram77 for the contribution (#2120)
• Minimum Go version is now 1.26 (#2146)
• Bump klauspost/compress to v1.20.0 and nkeys to v0.4.16 (#2117, #2146)
• Tests run locally without docker via an in-process ntf tester (#2131), and CI now runs against nats-server v2.15.0 (#2146)
• Fix flaky cluster restart tests (#2141) and list consumers test against latest server (#2138)

Complete Changes

nats-io/nats.go@v1.53.1...v1.54.0

Commits

• 7a8404a Release v1.54.0 (#2148)
• 240fb1f [IMPROVED] Bump dependencies and update server version in CI (#2146)
• 203d828 [FIXED] Panic in DecodeHeadersMsg on status tokens shorter than 3 characters ...
• dc92fca [FIXED] Ordered consumer silently losing messages on slow consumer (#2137)
• e18cea8 [IMPROVED] Prevent doErr closure escaping to heap (#2127)
• d8d8c09 [ADDED] nats.MultipathTCP() for enabling or disabling MPTCP (#2145)
• e95c424 [FIXED] Flaky cluster restart tests: waitForStream must see a stream leader (...
• e3abbf4 [ADDED] Nats-Schedule-Rollup header const and publish options (#2142)
• f1289db [ADDED] Desired state, peer ID/pending and source seq in stream and consumer ...
• b84f783 Ignore Claude Code local files and .worktrees (#2140)
• Additional commits viewable in compare view

Updates github.com/rabbitmq/amqp091-go from 1.14.0 to 1.15.0

Release notes

Sourced from github.com/rabbitmq/amqp091-go's releases.

v1.15.0

What's Changed

• chore(deps): bump github/codeql-action from 4.37.6 to 4.37.7 in the github-actions group by @​dependabot[bot] in rabbitmq/amqp091-go#385
• chore(deps): bump github/codeql-action from 4.37.7 to 4.37.8 in the github-actions group by @​dependabot[bot] in rabbitmq/amqp091-go#386
• fix: clone SASL authentication before zeroing credentials post-handshake by @​suchitd in rabbitmq/amqp091-go#388
• fix: preserve caller-provided SASL credentials across Reconnect() by @​suchitd in rabbitmq/amqp091-go#389
• chore(deps): bump github/codeql-action from 4.37.8 to 4.37.9 in the github-actions group by @​dependabot[bot] in rabbitmq/amqp091-go#390

Full Changelog: rabbitmq/amqp091-go@v1.14.0...v1.15.0

Changelog

Sourced from github.com/rabbitmq/amqp091-go's changelog.

v1.15.0 (2026-09-15)

Full Changelog

Fixed bugs:

• fix: preserve caller-provided SASL credentials across Reconnect() #389 (suchitd)
• fix: clone SASL authentication before zeroing credentials post-handshake #388 (suchitd)

Closed issues:

• v1.13.0 (#350) zeroes caller-provided PlainAuth.Password, breaking auth on any reconnect that reuses the Config #387

Merged pull requests:

• chore(deps): bump github/codeql-action from 4.37.8 to 4.37.9 in the github-actions group #390 (dependabot[bot])
• chore(deps): bump github/codeql-action from 4.37.7 to 4.37.8 in the github-actions group #386 (dependabot[bot])
• chore(deps): bump github/codeql-action from 4.37.6 to 4.37.7 in the github-actions group #385 (dependabot[bot])

Commits

• ff03b2f Release v1.15.0
• 276f52e Merge pull request #390 from rabbitmq/dependabot/github_actions/github-action...
• ca02321 chore(deps): bump github/codeql-action in the github-actions group
• 4a2300f Merge pull request #389 from rabbitmq/fix/recovery-preserve-sasl
• bf771db docs: trim cloneAuthentication doc comment
• 54bd90e fix: preserve caller-provided SASL credentials across Reconnect()
• 5935ca1 fix: clone SASL authentication before zeroing credentials post-handshake (#388)
• 0e52b40 Merge pull request #386 from rabbitmq/dependabot/github_actions/github-action...
• 01c30ed chore(deps): bump github/codeql-action in the github-actions group
• 28da80d Merge pull request #385 from rabbitmq/dependabot/github_actions/github-action...
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2 from 1.46.0 to 1.47.1

Commits

• 52ba256 Release 2026-09-24
• 21223cd Regenerated Clients
• 84d89bd Update endpoints model
• d9c59ff Update API model
• 8fd86b1 feat: Add aws-chunked response decoding reader (#3563)
• ff3ac6f Release 2026-09-23
• e57d2ff Regenerated Clients
• ef6fdb9 Update endpoints model
• 385ab15 Update API model
• fafcb4f Checksum non-200 HTTP responses (#3564)
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/config from 1.33.3 to 1.33.6

Commits

• 52ba256 Release 2026-09-24
• 21223cd Regenerated Clients
• 84d89bd Update endpoints model
• d9c59ff Update API model
• 8fd86b1 feat: Add aws-chunked response decoding reader (#3563)
• ff3ac6f Release 2026-09-23
• e57d2ff Regenerated Clients
• ef6fdb9 Update endpoints model
• 385ab15 Update API model
• fafcb4f Checksum non-200 HTTP responses (#3564)
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/credentials from 1.20.3 to 1.20.6

Commits

• 27acb6b Release 2023-12-15
• d3d958f Regenerated Clients
• b9e42b1 Update endpoints model
• d61965f Update API model
• dca6a24 Release 2023-12-14
• 65183ed Regenerated Clients
• 9a01654 Update endpoints model
• 87eb076 Update API model
• aaea7b5 Release 2023-12-13
• 8b61d81 Regenerated Clients
• Additional commits viewable in compare view

Updates github.com/aws/aws-sdk-go-v2/service/sqs from 1.51.0 to 1.52.1

Commits

• 10c4487 Release 2024-03-15
• db0b1ab Regenerated Clients
• 92c0060 Update endpoints model
• e5bb86e Update API model
• 49b368e Release 2024-03-14
• 0aa6643 Regenerated Clients
• bb0d403 Update API model
• 7229e9c Merge pull request #2553 from aws/feat-deprec-iotroborunner
• 8fa1496 update changelog
• 4174347 add changelog
• Additional commits viewable in compare view

Updates github.com/jackc/pgx/v5 from 5.10.0 to 5.11.0

Release notes

Sourced from github.com/jackc/pgx/v5's releases.

v5.11.0

This release adds direct PostgreSQL type scanning through database/sql on Go 1.27, improves compatibility with libpq connection strings and PostgreSQL date/time values, and includes further decoder hardening. See Changes for connection-string and date/time behavior changes that may affect existing applications.

Features

• stdlib: support Go 1.27's driver.RowsColumnScanner, allowing PostgreSQL types such as arrays and ranges to be scanned directly into Go values without pgtype.Map.SQLScanner. Existing database/sql scalar conversions and sql.Scanner behavior are preserved. The minimum supported Go version remains 1.25.
• Add Rows.TypeMap to expose the type map used to decode rows, including rows created by RowsFromResultReader that have no underlying Conn. Custom implementations of Rows, including mocks, must add this method.
• pgconn: add Config.MaxProtocolMessageBodyLen to configure the maximum incoming protocol message body size (carter-ya)
• pgconn: add ErrReadOnlyConnection, ErrReadWriteConnection, ErrPrimaryConnection, and ErrStandbyConnection sentinel errors for target_session_attrs validation, allowing callers to use errors.Is (Adrian-Stefan Mares)
• pgxpool: accept pool_ping_timeout in connection strings to configure Config.PingTimeout. The default is zero; zero and negative durations mean no timeout (1991santhu)

Changes

• Name-based row-to-struct mapping now matches explicit db tags case-insensitively, with exact matches taking precedence so tags can still distinguish quoted column names that differ only by case (AlisinaDevelo)

• pgconn: resolve the OS user account only when no user is supplied by the connection string, environment, or service file, avoiding unnecessary account lookups and crashes in some restricted container environments. Home-directory defaults for password, service, and TLS files remain available independently of the account lookup. On Unix these now use $HOME rather than the OS account's home directory (Mohamed MAACHE)

• pgtype: date, timestamp and timestamptz text values are now parsed and written by a hand-written parser and encoder for PostgreSQL's ISO date/time format instead of time.Parse and time.Format. Go's layout language cannot express a variable-width year or the BC era, which is the root of the bugs below. The text scan path is roughly 2.5x faster for timestamp and timestamptz. Bug fixes:

  • timestamp and timestamptz no longer silently move February 29 of a BC leap year to March 1 when encoding. time.Date(-4712, 2, 29, ...) was written as 4713-03-01 BC and is now written as 4713-02-29 BC. This affected ordinary four-digit BC years, not only extended-range ones. date was never affected.
  • timestamp and timestamptz can now scan BC leap days. 4713-02-29 BC previously failed with day out of range. date could already scan them.
  • Years past 9999 can now be scanned. 10000-01-02 03:04:05 previously failed to parse, so timestamp and timestamptz values at the high end of PostgreSQL's range were unreadable over the simple protocol and in any other text-format result.
  • time.Time arguments in the simple protocol now encode BC dates correctly, using the same timestamp encoder.
  • Fractional seconds beyond microsecond precision are rounded the way the server rounds them (round half to even, carrying into the rest of the value) instead of being kept at full precision. PostgreSQL never sends more than six fractional digits, so this only affects values from other sources.

  Behavior changes:

  • date now rejects impossible dates instead of normalizing them. 2024-02-30 returned 2024-03-01 and 2024-13-01 returned 2025-01-01; both are now errors. timestamp and timestamptz already rejected them.
  • All three types now reject values outside PostgreSQL's range for that type, in the binary format as well as the text format. PostgreSQL never sends out-of-range dates, so this only affects corrupt or hand-built input; the range

... (truncated)

Changelog

Sourced from github.com/jackc/pgx/v5's changelog.

5.11.0 (September 7, 2026)

This release adds direct PostgreSQL type scanning through database/sql on Go 1.27, improves compatibility with libpq connection strings and PostgreSQL date/time values, and includes further decoder hardening. See Changes for connection-string and date/time behavior changes that may affect existing applications.

Features

• stdlib: support Go 1.27's driver.RowsColumnScanner, allowing PostgreSQL types such as arrays and ranges to be scanned directly into Go values without pgtype.Map.SQLScanner. Existing database/sql scalar conversions and sql.Scanner behavior are preserved. The minimum supported Go version remains 1.25.
• Add Rows.TypeMap to expose the type map used to decode rows, including rows created by RowsFromResultReader that have no underlying Conn. Custom implementations of Rows, including mocks, must add this method.
• pgconn: add Config.MaxProtocolMessageBodyLen to configure the maximum incoming protocol message body size (carter-ya)
• pgconn: add ErrReadOnlyConnection, ErrReadWriteConnection, ErrPrimaryConnection, and ErrStandbyConnection sentinel errors for target_session_attrs validation, allowing callers to use errors.Is (Adrian-Stefan Mares)
• pgxpool: accept pool_ping_timeout in connection strings to configure Config.PingTimeout. The default is zero; zero and negative durations mean no timeout (1991santhu)

Changes

• Name-based row-to-struct mapping now matches explicit db tags case-insensitively, with exact matches taking precedence so tags can still distinguish quoted column names that differ only by case (AlisinaDevelo)

• pgconn: resolve the OS user account only when no user is supplied by the connection string, environment, or service file, avoiding unnecessary account lookups and crashes in some restricted container environments. Home-directory defaults for password, service, and TLS files remain available independently of the account lookup. On Unix these now use $HOME rather than the OS account's home directory (Mohamed MAACHE)

• pgtype: date, timestamp and timestamptz text values are now parsed and written by a hand-written parser and encoder for PostgreSQL's ISO date/time format instead of time.Parse and time.Format. Go's layout language cannot express a variable-width year or the BC era, which is the root of the bugs below. The text scan path is roughly 2.5x faster for timestamp and timestamptz. Bug fixes:

  • timestamp and timestamptz no longer silently move February 29 of a BC leap year to March 1 when encoding. time.Date(-4712, 2, 29, ...) was written as 4713-03-01 BC and is now written as 4713-02-29 BC. This affected ordinary four-digit BC years, not only extended-range ones. date was never affected.
  • timestamp and timestamptz can now scan BC leap days. 4713-02-29 BC previously failed with day out of range. date could already scan them.
  • Years past 9999 can now be scanned. 10000-01-02 03:04:05 previously failed to parse, so timestamp and timestamptz values at the high end of PostgreSQL's range were unreadable over the simple protocol and in any other text-format result.
  • time.Time arguments in the simple protocol now encode BC dates correctly, using the same timestamp encoder.
  • Fractional seconds beyond microsecond precision are rounded the way the server rounds them (round half to even, carrying into the rest of the value) instead of being kept at full precision. PostgreSQL never sends more than six fractional digits, so this only affects values from other sources.

  Behavior changes:

  • date now rejects impossible dates instead of normalizing them. 2024-02-30 returned 2024-03-01 and 2024-13-01 returned 2025-01-01; both are now errors. timestamp and timestamptz already rejected them.
  • All three types now reject values outside PostgreSQL's range for that type, in the binary format as well as the

... (truncated)

Commits

• 5e583fa Update changelog for v5.11.0
• 3927116 Apply gofumpt formatting required by lint
• eb07165 Quote filesystem paths in development connection strings
• cf5938f Allow unsigned digit counts in binary numeric encoding
• 3930cf5 Accept PostgreSQL POSIX timezone offsets in text timestamps
• 93261be Prefer exact db tag matches when mapping rows to structs
• e8d8ad1 Merge pull request #2647 from sueun-dev/fix-range-text-quoting-20260906
• 01d2fd3 Merge pull request #2644 from eliranbz/fix-failed-prepare-deallocation
• 9b7e3be Merge pull request #2645 from ash2k/move-channel
• 76d78f5 Merge pull request #2643 from AshSgDe29071999/fix/hstore-pairs-estimate-clamp
• Additional commits viewable 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