Skip to content

Bump the go-dependencies group across 2 directories with 6 updates - #431

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

Bump the go-dependencies group across 2 directories with 6 updates#431
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/go_modules/go-dependencies-dbcfd161d3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 15, 2025

Copy link
Copy Markdown
Contributor

Bumps the go-dependencies group with 2 updates in the / directory: github.com/riverqueue/river and github.com/samber/slog-http.
Bumps the go-dependencies group with 2 updates in the /riverproui directory: github.com/riverqueue/river and github.com/samber/slog-http.

Updates github.com/riverqueue/river from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

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

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/riverdriver from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

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

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/riverdriver/riverpgxv5 from 0.24.0 to 0.25.0

Release notes

Sourced from github.com/riverqueue/river/riverdriver/riverpgxv5's releases.

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

Sourced from github.com/riverqueue/river/riverdriver/riverpgxv5's changelog.

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/rivershared from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

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

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/rivertype from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

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

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/samber/slog-http from 1.8.1 to 1.8.2

Release notes

Sourced from github.com/samber/slog-http's releases.

v1.8.2

fix: fix out of bounds slice

Commits

Updates github.com/riverqueue/river from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

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

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/riverdriver from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

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

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/riverdriver/riverpgxv5 from 0.24.0 to 0.25.0

Release notes

Sourced from github.com/riverqueue/river/riverdriver/riverpgxv5's releases.

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

Sourced from github.com/riverqueue/river/riverdriver/riverpgxv5's changelog.

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/rivershared from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Changelog

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

[0.25.0] - 2025-09-14

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR #1025](riverqueue/river#1025).
  • When snoozing a job with zero duration so that it's retried immediately, subscription events no longer appear incorrectly with a kind of rivertype.EventKindJobFailed. Instead they're assigned rivertype.EventKindJobSnoozed just like they would have with a non-zero snooze duration. [PR #1037](riverqueue/river#1037).
Commits
  • 96877cf Prepare release v0.25.0 (#1042)
  • e1e8089 Bump the go-dependencies group across 6 directories with 1 update (#1041)
  • 782bca5 JobUpdate: add max attempts and metadata attrs (#1039)
  • a360e93 fix flaky job snooze 0 duration test (#1040)
  • 35514f2 Cleanly handle jobs being snoozed with zero duration (#1037)
  • d5410e9 Require use of JobDeleteManyParams.UnsafeAll to delete all jobs (#1033)
  • a698036 Bump the go-dependencies group across 9 directories with 5 updates (#1032)
  • fc65bb4 stronger test coverage around JobDeleteMany (#1030)
  • 9451ded consolidate JobDeleteMany logic (#1029)
  • 2e097a8 Add lazy slice formatters to slogutil (#1028)
  • Additional commits viewable in compare view

Updates github.com/riverqueue/river/rivertype from 0.24.0 to 0.25.0

Release notes

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

v0.25.0

⚠️ Internal APIs used for communication between River and River Pro have changed. If using River Pro, make sure to update River and River Pro to latest at the same time to get compatible versions. River v0.25.0 is compatible with River Pro v0.18.0.

Changed

  • Set minimum Go version to Go 1.24. [PR #1032](riverqueue/river#1032).
  • Breaking change: Client.JobDeleteMany now requires the use of JobDeleteManyParams.UnsafeAll to delete all jobs without a filter applied. This is a safety feature to make it more difficult to accidentally delete all non-running jobs. This is a minor breaking change, but on a fairly new feature that's not likely to be used on purpose by very many people yet. [PR #1033](riverqueue/river#1033).

Fixed

  • Don't double log fetch errors. [PR

Bumps the go-dependencies group with 2 updates in the / directory: [github.com/riverqueue/river](https://github.com/riverqueue/river) and [github.com/samber/slog-http](https://github.com/samber/slog-http).
Bumps the go-dependencies group with 2 updates in the /riverproui directory: [github.com/riverqueue/river](https://github.com/riverqueue/river) and [github.com/samber/slog-http](https://github.com/samber/slog-http).


Updates `github.com/riverqueue/river` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/riverdriver` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/riverdriver/riverpgxv5` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/rivershared` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/rivertype` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/samber/slog-http` from 1.8.1 to 1.8.2
- [Release notes](https://github.com/samber/slog-http/releases)
- [Commits](samber/slog-http@v1.8.1...v1.8.2)

Updates `github.com/riverqueue/river` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/riverdriver` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/riverdriver/riverpgxv5` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/rivershared` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/riverqueue/river/rivertype` from 0.24.0 to 0.25.0
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.24.0...v0.25.0)

Updates `github.com/samber/slog-http` from 1.8.1 to 1.8.2
- [Release notes](https://github.com/samber/slog-http/releases)
- [Commits](samber/slog-http@v1.8.1...v1.8.2)

---
updated-dependencies:
- dependency-name: github.com/riverqueue/river
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/riverdriver
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/riverdriver/riverpgxv5
  dependency-version: 0.25.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.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/rivertype
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/samber/slog-http
  dependency-version: 1.8.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/riverdriver
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/riverdriver/riverpgxv5
  dependency-version: 0.25.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/rivershared
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/riverqueue/river/rivertype
  dependency-version: 0.25.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-dependencies
- dependency-name: github.com/samber/slog-http
  dependency-version: 1.8.2
  dependency-type: indirect
  update-type: version-update:semver-patch
  dependency-group: go-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Sep 15, 2025
@dependabot @github

dependabot Bot commented on behalf of github Sep 21, 2025

Copy link
Copy Markdown
Contributor Author

Dependabot can't resolve your Go dependency files. Because of this, Dependabot cannot update this pull request.

@dependabot @github

dependabot Bot commented on behalf of github Sep 21, 2025

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are no longer updatable, so this is no longer needed.

@dependabot dependabot Bot closed this Sep 21, 2025
@dependabot
dependabot Bot deleted the dependabot/go_modules/go-dependencies-dbcfd161d3 branch September 21, 2025 18:58
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