Skip to content

Bump the go-dependencies group across 1 directory with 3 updates - #60

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/go_modules/go-dependencies-5dfae5a607
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/go_modules/go-dependencies-5dfae5a607

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026

Copy link
Copy Markdown
Contributor

Bumps the go-dependencies group with 3 updates in the / directory: github.com/go-playground/validator/v10, github.com/jackc/pgx/v5 and github.com/riverqueue/river/rivershared.

Updates github.com/go-playground/validator/v10 from 10.30.5 to 10.30.6

Release notes

Sourced from github.com/go-playground/validator/v10's releases.

v10.30.6

What's Changed

New Contributors

Full Changelog: go-playground/validator@v10.30.5...v10.30.6

Commits
  • 19397f2 Add uuid7 validation tag (#1614)
  • 5b09d8d Convert to time.Time before asserting in isNeField (#1619)
  • 563e738 fix: reject duplicate variants in strict BCP47 tags (#1678)
  • 0f885d2 fix: reject ULIDs outside the 128-bit range (#1660)
  • c9cfe75 fix: anchor GB and LI postcode patterns as a whole (#1646)
  • 29d05a7 docs: fix stale alias, uuid and snippet details in package docs (#1679)
  • 0411012 chore(deps): bump github.com/gabriel-vasile/mimetype from 1.4.15 to 1.4.16 (#...
  • a5843c6 Add postcode patterns for IE (Ireland), AL (Albania), GI (Gibraltar) and IL (...
  • c29fac1 Clarify separators for non-existent directory paths (#1672)
  • 3b54840 ci: send coverage from the Go 1.26.x leg (step skipped since #1535) (#1671)
  • Additional commits viewable in compare view

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

Changelog

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

5.13.0 (November 11, 2026)

This release adds automatic client certificate reloading and temporal precision metadata for database/sql. It also fixes a panic on malformed server responses, unsafe retries after connection failures, and range encoding. See Changes for client certificate configuration behavior that may affect existing applications.

Security Fixes

  • Panic in Rows.Values on malformed server responses (GHSA-w9rp-vfrh-q8vv). A server response containing fewer row values than declared fields could cause an index-out-of-range panic in Rows.Values. It now returns an error and closes the rows when the counts differ, including when there are extra values, matching Rows.Scan validation.

Features

  • pgconn: reload client certificates and keys configured through sslcert and sslkey for each TLS certificate request, allowing new connections to pick up rotated credentials without recreating the configuration or restarting the application. Files are still validated during configuration parsing. Relative paths retain their parse-time directory, and reloads follow symlinks (Erin Shepherd)
  • stdlib: expose fractional seconds precision for timestamp, timestamptz, time, timetz, and interval through ColumnTypePrecisionScale and database/sql.ColumnType.DecimalSize. These return precision 0, the fractional seconds precision as scale, and ok=true. The scale defaults to 6 when no fractional seconds precision is declared; precision 0 means numeric precision is not applicable (Danny Xu)

Changes

  • pgconn: file-backed client certificates are no longer stored in the parsed TLSConfig.Certificates slice. Setting TLSConfig.Certificates (including a non-nil empty slice) or TLSConfig.GetClientCertificate overrides automatic reloading. Replacing TLSConfig, including with a direct TLSConfig.Clone, discards the file-backed certificate settings; use pgconn.Config.Copy to preserve them when copying a configuration. Certificate and key files must remain readable for subsequent TLS certificate requests. Encrypted keys reuse the password resolved during configuration parsing; GetSSLPassword is not called again on reload.

Bug Fixes

  • pgconn: do not mark a connection-closed error encountered while receiving a response as safe to retry, since the request may already have reached the server. This prevents database/sql from automatically repeating a statement that may already have executed. The error still supports errors.Is(err, pgconn.ErrConnClosed) (Aayush Shah)
  • pgconn: skip sending a cancel request when a connection fails during startup, avoiding an unnecessary second connection attempt (felipe stival)
  • pgconn: accept unencrypted combined certificate/key PEM files with the certificate before the key, as well as key-first files (Erin Shepherd)
  • pgtype: encode Range[any] values returned by RangeCodec.DecodeValue and Rows.Values in both binary and text formats, allowing decoded ranges and multiranges to be reused as query arguments or in CopyFrom (waw666waw666)
  • stdlib: report ok=false for the precision and scale of unconstrained numeric columns instead of bogus values (Danny Xu)
  • stdlib: report math.MaxInt64 for the lengths of unconstrained varchar, bpchar, and varbit columns instead of negative lengths (PerryLink)

... (truncated)

Commits
  • 1e38d71 Update changelog for v5.13.0
  • e2bb010 Fix Rows.Values panic on mismatched field counts
  • 5b0fd94 Merge pull request #2709 from waw666waw666/fix-range-any-encode
  • 427f50d Merge pull request #2715 from v0idpwn/pgconn-no-cancel-on-failed-connect
  • 86b4411 Merge pull request #2713 from ksamirdev/fix-append-rows-by-name-bench
  • a3b88dc Merge pull request #2714 from PerryLink/stdlib-column-type-length-unbounded
  • 2f429e5 Merge pull request #2710 from dajiaohuang/codex/2705-pingtimeout-docs
  • 85c3e62 stdlib: close rows in precision and scale test
  • 4f41feb stdlib: clarify zero precision for temporal types
  • 22ccfd1 stdlib: document temporal precision and scale metadata
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/rivershared from 0.48.0 to 0.51.2

Release notes

Sourced from github.com/riverqueue/river/rivershared's releases.

v0.51.2

Fixed

  • Accept sqlite:path and sqlite::memory: in the CLI alongside the existing sqlite:// forms, including offline migration SQL export. [PR #1588](riverqueue/river#1588).
  • Reject empty SQLite paths in commands that connect to a database; bare prefixes remain valid for offline migration SQL export. [PR #1588](riverqueue/river#1588).
  • Fixed JobListParams.Where writing into the first NamedArgs it's given when merging multiple sets of named arguments, which could leak arguments into a map the caller reused for another query. It also no longer panics when the first set is nil. [PR #1575](riverqueue/river#1575).

v0.51.1

Fixed

  • Fixed a client ignoring queue pause, resume, or metadata changes until it restarted when the queue control notification was lost, as happens if it's sent while the client's notifier is reconnecting. Clients with a notifier now also check their queues' settings once a minute. [Issue #1579](riverqueue/river#1579).
  • Fixed the notifier never reconnecting when its connection went silent without an error, like after a dropped network path, because its health check ping had no timeout. The ping now times out after 10 seconds. [Issue #1579](riverqueue/river#1579).
  • Fixed maintenance services logging errors during normal shutdown or leadership loss, including PeriodicJobEnqueuer reporting Error starting transaction: context canceled when stopped during staggered startup. Genuine query timeouts and database failures are still logged, and periodic job transactions now roll back even after cancellation. [PR #1577](riverqueue/river#1577).

v0.51.0

Added

  • Added JobDeleteManyParams.Where, an escape hatch for deleting jobs by an arbitrary SQL predicate, like JobListParams.Where does for lists. For example, it can select queued jobs whose args name a given customer. A Where predicate counts as a filter, so it doesn't need UnsafeAll, and each predicate is wrapped in parentheses so that an OR in it can't widen the deletion past other filters or to running jobs. The existing batch limit (100 jobs by default) and Postgres behavior of skipping locked jobs still apply. [PR #1570](riverqueue/river#1570).

Fixed

  • Fixed a running job not being cancelled after Client.JobCancel when the cancellation notification was lost, as happens if it's sent while the client's notifier is reconnecting. Clients with a notifier now also check their running jobs for cancellation requests once a minute. Client.JobRetry now clears an earlier attempt's cancellation request so that the retried job isn't cancelled again. [PR #1564](riverqueue/river#1564).
  • Fixed Client.InsertManyFast panicking after its transaction committed on a client configured with queues when the driver doesn't support a listener, such as a riverdatabasesql driver created with New instead of NewWithPgxListener. It now wakes producers for the inserted jobs' queues right away, like Client.InsertMany. [PR #1558](riverqueue/river#1558).
  • Fixed Client.QueueUpdate without metadata crashing the program when the client works that queue and the driver doesn't support a listener. [PR #1558](riverqueue/river#1558).
  • Fixed the notifier's run loop blocking forever when a topic LISTEN or UNLISTEN handed to it finished after its caller had stopped waiting (after 5 seconds, with timed out waiting for interrupt operation), as can happen on a slow or unresponsive connection. Client.Stop then never completed, and neither did a Client.Start that failed this way. [PR #1559](riverqueue/river#1559).

v0.50.0

Changed

  • Breaking: Resumable steps can no longer be nested. Calls fail before running child callbacks, preventing unreachable resume points and rolled-back parent checkpoints from being saved again. [PR #1534](riverqueue/river#1534).
  • Job deletion through Client.JobDelete, Client.JobDeleteMany, their Tx variants, and the job cleaner now goes through optional pilot hooks, so a pilot can take part in deletes as it already can in cancels and retries. Behavior with the standard pilot is unchanged. [PR #1500](riverqueue/river#1500).

Fixed

  • Refresh a durable periodic job's saved row only after its next run time is loaded at startup or committed. When a startup write rolled back, keep-alive could revive an expired row, and the next leader enqueued every run since the row's old next run time. [PR #1540](riverqueue/river#1540).
  • Fail retries that omit a saved cursor-only step, while preserving their checkpoints for recovery. Jobs with an existing step marker retain their behavior, including legacy stale cursor entries. [PR #1534](riverqueue/river#1534).
  • Fixed SQLite metadata updates recursively merging nested objects and deleting keys set to JSON null. Updates now replace whole top-level values, matching Postgres and preventing completed resumable cursor steps from running again on later retries. [PR #1533](riverqueue/river#1533).
  • Fixed resumable transactional checkpoints being saved again after rollback or a failed write, and first-step cursors being lost on error, snooze, or cooperative shutdown. After a successful checkpoint write, the caller's transaction owns that progress; rollback may replay earlier unpersisted steps. The Rust, JavaScript, and Java runtimes now share the applicable behavior, including preserving progress on snooze. [PR #1521](riverqueue/river#1521).
  • Fixed AddWorkerSafely leaving a worker's primary kind and earlier aliases registered when a later kind alias conflicts with an existing registration. Failed registrations now leave the worker registry unchanged. [PR #1440](riverqueue/river#1440).
  • Fixed the notifier retrying without backoff and flooding logs when the context passed to Client.Start reaches its deadline. [PR #1495](riverqueue/river#1495).
  • Fixed JobSnooze accepting negative durations despite documenting that they panic. [PR #1529](riverqueue/river#1529).

v0.49.0

⚠️ If using River Pro, make sure to upgrade it to at least River Pro v0.32.0 to get a compatible package.

Changed

  • Internal transaction helpers now reuse existing transactions instead of creating unnecessary savepoints. Callers of transactional APIs must roll back their transaction on error; applications that need partial rollback can create an explicit savepoint around the River call. Set RIVER_USE_LEGACY_SUBTRANSACTIONS=1 (or true) before starting the application to restore savepoints in these helpers, including those used by River Pro. This is a temporary compatibility fallback planned for removal in a future release. [PR #1420](riverqueue/river#1420).

Fixed

... (truncated)

Changelog

Sourced from github.com/riverqueue/river/rivershared's changelog.

[0.51.2] - 2026-11-09

Fixed

  • Accept sqlite:path and sqlite::memory: in the CLI alongside the existing sqlite:// forms, including offline migration SQL export. [PR #1588](riverqueue/river#1588).
  • Reject empty SQLite paths in commands that connect to a database; bare prefixes remain valid for offline migration SQL export. [PR #1588](riverqueue/river#1588).
  • Fixed JobListParams.Where writing into the first NamedArgs it's given when merging multiple sets of named arguments, which could leak arguments into a map the caller reused for another query. It also no longer panics when the first set is nil. [PR #1575](riverqueue/river#1575).

[0.51.1] - 2026-11-05

Fixed

  • Fixed a client ignoring queue pause, resume, or metadata changes until it restarted when the queue control notification was lost, as happens if it's sent while the client's notifier is reconnecting. Clients with a notifier now also check their queues' settings once a minute. [Issue #1579](riverqueue/river#1579).
  • Fixed the notifier never reconnecting when its connection went silent without an error, like after a dropped network path, because its health check ping had no timeout. The ping now times out after 10 seconds. [Issue #1579](riverqueue/river#1579).
  • Fixed maintenance services logging errors during normal shutdown or leadership loss, including PeriodicJobEnqueuer reporting Error starting transaction: context canceled when stopped during staggered startup. Genuine query timeouts and database failures are still logged, and periodic job transactions now roll back even after cancellation. [PR #1577](riverqueue/river#1577).

[0.51.0] - 2026-10-31

Added

  • Added JobDeleteManyParams.Where, an escape hatch for deleting jobs by an arbitrary SQL predicate, like JobListParams.Where does for lists. For example, it can select queued jobs whose args name a given customer. A Where predicate counts as a filter, so it doesn't need UnsafeAll, and each predicate is wrapped in parentheses so that an OR in it can't widen the deletion past other filters or to running jobs. The existing batch limit (100 jobs by default) and Postgres behavior of skipping locked jobs still apply. [PR #1570](riverqueue/river#1570).

Fixed

  • Fixed a running job not being cancelled after Client.JobCancel when the cancellation notification was lost, as happens if it's sent while the client's notifier is reconnecting. Clients with a notifier now also check their running jobs for cancellation requests once a minute. Client.JobRetry now clears an earlier attempt's cancellation request so that the retried job isn't cancelled again. [PR #1564](riverqueue/river#1564).
  • Fixed Client.InsertManyFast panicking after its transaction committed on a client configured with queues when the driver doesn't support a listener, such as a riverdatabasesql driver created with New instead of NewWithPgxListener. It now wakes producers for the inserted jobs' queues right away, like Client.InsertMany. [PR #1558](riverqueue/river#1558).
  • Fixed Client.QueueUpdate without metadata crashing the program when the client works that queue and the driver doesn't support a listener. [PR #1558](riverqueue/river#1558).
  • Fixed the notifier's run loop blocking forever when a topic LISTEN or UNLISTEN handed to it finished after its caller had stopped waiting (after 5 seconds, with timed out waiting for interrupt operation), as can happen on a slow or unresponsive connection. Client.Stop then never completed, and neither did a Client.Start that failed this way. [PR #1559](riverqueue/river#1559).

[0.50.0] - 2026-10-26

Changed

  • Breaking: Resumable steps can no longer be nested. Calls fail before running child callbacks, preventing unreachable resume points and rolled-back parent checkpoints from being saved again. [PR #1534](riverqueue/river#1534).
  • Job deletion through Client.JobDelete, Client.JobDeleteMany, their Tx variants, and the job cleaner now goes through optional pilot hooks, so a pilot can take part in deletes as it already can in cancels and retries. Behavior with the standard pilot is unchanged. [PR #1500](riverqueue/river#1500).

Fixed

  • Refresh a durable periodic job's saved row only after its next run time is loaded at startup or committed. When a startup write rolled back, keep-alive could revive an expired row, and the next leader enqueued every run since the row's old next run time. [PR #1540](riverqueue/river#1540).
  • Fail retries that omit a saved cursor-only step, while preserving their checkpoints for recovery. Jobs with an existing step marker retain their behavior, including legacy stale cursor entries. [PR #1534](riverqueue/river#1534).
  • Fixed SQLite metadata updates recursively merging nested objects and deleting keys set to JSON null. Updates now replace whole top-level values, matching Postgres and preventing completed resumable cursor steps from running again on later retries. [PR #1533](riverqueue/river#1533).
  • Fixed resumable transactional checkpoints being saved again after rollback or a failed write, and first-step cursors being lost on error, snooze, or cooperative shutdown. After a successful checkpoint write, the caller's transaction owns that progress; rollback may replay earlier unpersisted steps. The Rust, JavaScript, and Java runtimes now share the applicable behavior, including preserving progress on snooze. [PR #1521](riverqueue/river#1521).
  • Fixed AddWorkerSafely leaving a worker's primary kind and earlier aliases registered when a later kind alias conflicts with an existing registration. Failed registrations now leave the worker registry unchanged. [PR #1440](riverqueue/river#1440).
  • Fixed the notifier retrying without backoff and flooding logs when the context passed to Client.Start reaches its deadline. [PR #1495](riverqueue/river#1495).
  • Fixed JobSnooze accepting negative durations despite documenting that they panic. [PR #1529](riverqueue/river#1529).

[0.49.0] - 2026-10-05

⚠️ If using River Pro, make sure to upgrade it to at least River Pro v0.32.0 to get a compatible package.

... (truncated)

Commits
  • 8468ff2 [go] Prepare v0.51.2 (#1590)
  • 60004e3 Align SQLite CLI URL forms across languages (#1588)
  • 6a1d035 [go] Stop JobListParams.Where from mutating caller named args (#1575)
  • 72ba253 [java] Prepare v0.4.0 (#1587)
  • 1b26d3b [java] Isolate batch peer decoding failures (#1586)
  • 03b193e [rust] Prepare v0.6.0 (#1585)
  • 7e514e0 [rust] Implement river migrate-get subcommand for Rust CLI (#1584)
  • 6c72392 [go, js, rust] Prepare v0.51.1, v0.3.1, and v0.5.1
  • 9db53b9 [go, js, rust] Fix context canceled problem in start when stopping (#1577)
  • 43e6f22 Poll queue settings as a fallback when a notifier is configured (#1582)
  • 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

Bumps the go-dependencies group with 3 updates in the / directory: [github.com/go-playground/validator/v10](https://github.com/go-playground/validator), [github.com/jackc/pgx/v5](https://github.com/jackc/pgx) and [github.com/riverqueue/river/rivershared](https://github.com/riverqueue/river).


Updates `github.com/go-playground/validator/v10` from 10.30.5 to 10.30.6
- [Release notes](https://github.com/go-playground/validator/releases)
- [Commits](go-playground/validator@v10.30.5...v10.30.6)

Updates `github.com/jackc/pgx/v5` from 5.11.0 to 5.13.0
- [Release notes](https://github.com/jackc/pgx/releases)
- [Changelog](https://github.com/jackc/pgx/blob/master/CHANGELOG.md)
- [Commits](jackc/pgx@v5.11.0...v5.13.0)

Updates `github.com/riverqueue/river/rivershared` from 0.48.0 to 0.51.2
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.48.0...v0.51.2)

---
updated-dependencies:
- dependency-name: github.com/go-playground/validator/v10
  dependency-version: 10.30.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-dependencies
- dependency-name: github.com/jackc/pgx/v5
  dependency-version: 5.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/rivershared
  dependency-version: 0.51.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants