Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump github.com/riverqueue/river/riverdriver/riverpgxv5 from 0.14.1 to 0.16.0 #60

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 3, 2025

Bumps github.com/riverqueue/river/riverdriver/riverpgxv5 from 0.14.1 to 0.16.0.

Release notes

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

v0.16.0

Added

  • NeverSchedule returns a PeriodicSchedule that never runs. This can be used to effectively disable the reindexer or any other maintenance service. [PR #718](riverqueue/river#718).
  • Add SkipUnknownJobCheck client config option to skip job arg worker validation. [PR #731](riverqueue/river#731).

Changed

  • The reindexer maintenance process has been enabled. As of now, it will reindex only the river_job_args_index and river_jobs_metadata_index GIN indexes, which are more prone to bloat than b-tree indexes. By default it runs daily at midnight UTC, but can be customized on the river.Config type via ReindexerSchedule. Most installations will benefit from this process, but it can be disabled altogether using NeverSchedule. [PR #718](riverqueue/river#718).

  • Periodic jobs now have a "periodic": true attribute set in their metadata to make them more easily distinguishable from other types of jobs. [PR #728](riverqueue/river#728).

  • Snoozing a job now causes its attempt to be decremented, whereas previously the max_attempts would be incremented. In either case, this avoids allowing a snooze to exhaust a job's retries; however the new behavior also avoids potential issues with wrapping the max_attempts value, and makes it simpler to implement a RetryPolicy based on either attempt or max_attempts. The number of snoozes is also tracked in the job's metadata as snoozes for debugging purposes.

    The implementation of the builtin RetryPolicy implementations is not changed, so this change should not cause any user-facing breakage unless you're relying on attempt - len(errors) for some reason. [PR #730](riverqueue/river#730).

  • ByPeriod uniqueness is now based off a job's ScheduledAt instead of the current time if it has a value. [PR #734](riverqueue/river#734).

v0.15.0

Added

  • The River CLI will now respect the standard set of PG* environment variables like PGHOST, PGPORT, PGDATABASE, PGUSER, PGPASSWORD, and PGSSLMODE to configure a target database when the --database-url parameter is omitted. [PR #702](riverqueue/river#702).
  • Add missing doc for JobRow.UniqueStates + reveal rivertype.UniqueOptsByStateDefault() to provide access to the default set of unique job states. [PR #707](riverqueue/river#707).

Changed

  • Sleep durations are now logged as Go-like duration strings (e.g. "10s") in either text or JSON instead of duration strings in text and nanoseconds in JSON. [PR #699](riverqueue/river#699).
  • Altered the migration comments from river migrate-get to include the "line" of the migration being run (main, or for River Pro workflow and sequence) to make them more distinguishable. [PR #703](riverqueue/river#703).
  • Fewer slice allocations during unique insertions. [PR #705](riverqueue/river#705).

Fixed

  • Exponential backoffs at degenerately high job attempts (>= 310) no longer risk overflowing time.Duration. [PR #698](riverqueue/river#698).

v0.14.3

Changed

  • Dropped internal random generators in favor of math/rand/v2, which will have the effect of making code fully incompatible with Go 1.21 (go.mod has specified a minimum of 1.22 for some time already though). [PR #691](riverqueue/river#691).

Fixed

  • 006 migration now tolerates previous existence of a unique_states column in case it was added separately so that the new index could be raised with CONCURRENTLY. [PR #690](riverqueue/river#690).

v0.14.2

Fixed

  • Cancellation of running jobs relied on a channel that was only being received when in the job fetch routine, meaning that jobs which were cancelled would not be cancelled until the next scheduled fetch. This was fixed by also receiving from the job cancellation channel when in the main producer loop, even if no fetches are happening. [PR #678](riverqueue/river#678).
  • Job insert middleware were not being utilized for periodic jobs. This insertion path has been refactored to rely on the unified insertion path from the client. Fixes #675. [PR #679](riverqueue/river#679).
Changelog

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

[0.16.0] - 2024-01-27

Added

  • NeverSchedule returns a PeriodicSchedule that never runs. This can be used to effectively disable the reindexer or any other maintenance service. [PR #718](riverqueue/river#718).
  • Add SkipUnknownJobCheck client config option to skip job arg worker validation. [PR #731](riverqueue/river#731).

Changed

  • The reindexer maintenance process has been enabled. As of now, it will reindex only the river_job_args_index and river_jobs_metadata_index GIN indexes, which are more prone to bloat than b-tree indexes. By default it runs daily at midnight UTC, but can be customized on the river.Config type via ReindexerSchedule. Most installations will benefit from this process, but it can be disabled altogether using NeverSchedule. [PR #718](riverqueue/river#718).

  • Periodic jobs now have a "periodic": true attribute set in their metadata to make them more easily distinguishable from other types of jobs. [PR #728](riverqueue/river#728).

  • Snoozing a job now causes its attempt to be decremented, whereas previously the max_attempts would be incremented. In either case, this avoids allowing a snooze to exhaust a job's retries; however the new behavior also avoids potential issues with wrapping the max_attempts value, and makes it simpler to implement a RetryPolicy based on either attempt or max_attempts. The number of snoozes is also tracked in the job's metadata as snoozes for debugging purposes.

    The implementation of the builtin RetryPolicy implementations is not changed, so this change should not cause any user-facing breakage unless you're relying on attempt - len(errors) for some reason. [PR #730](riverqueue/river#730).

  • ByPeriod uniqueness is now based off a job's ScheduledAt instead of the current time if it has a value. [PR #734](riverqueue/river#734).

[0.15.0] - 2024-12-26

Added

  • The River CLI will now respect the standard set of PG* environment variables like PGHOST, PGPORT, PGDATABASE, PGUSER, PGPASSWORD, and PGSSLMODE to configure a target database when the --database-url parameter is omitted. [PR #702](riverqueue/river#702).
  • Add missing doc for JobRow.UniqueStates + reveal rivertype.UniqueOptsByStateDefault() to provide access to the default set of unique job states. [PR #707](riverqueue/river#707).

Changed

  • Sleep durations are now logged as Go-like duration strings (e.g. "10s") in either text or JSON instead of duration strings in text and nanoseconds in JSON. [PR #699](riverqueue/river#699).
  • Altered the migration comments from river migrate-get to include the "line" of the migration being run (main, or for River Pro workflow and sequence) to make them more distinguishable. [PR #703](riverqueue/river#703).
  • Fewer slice allocations during unique insertions. [PR #705](riverqueue/river#705).

Fixed

  • Exponential backoffs at degenerately high job attempts (>= 310) no longer risk overflowing time.Duration. [PR #698](riverqueue/river#698).

[0.14.3] - 2024-12-14

Changed

  • Dropped internal random generators in favor of math/rand/v2, which will have the effect of making code fully incompatible with Go 1.21 (go.mod has specified a minimum of 1.22 for some time already though). [PR #691](riverqueue/river#691).

Fixed

  • 006 migration now tolerates previous existence of a unique_states column in case it was added separately so that the new index could be raised with CONCURRENTLY. [PR #690](riverqueue/river#690).

[0.14.2] - 2024-11-16

Fixed

  • Cancellation of running jobs relied on a channel that was only being received when in the job fetch routine, meaning that jobs which were cancelled would not be cancelled until the next scheduled fetch. This was fixed by also receiving from the job cancellation channel when in the main producer loop, even if no fetches are happening. [PR #678](riverqueue/river#678).
  • Job insert middleware were not being utilized for periodic jobs. This insertion path has been refactored to rely on the unified insertion path from the client. Fixes #675. [PR #679](riverqueue/river#679).
Commits
  • 8043b57 prepare v0.16.0 (#735)
  • ee4cbd4 Allow by period uniqueness to be based off scheduled time (#734)
  • 4cea55a Update golangci-lint to v1.63.4 (#733)
  • 5385fab go work sync && make tidy (#732)
  • fdbc2dd feat(config): add SkipUnknownJobCheck client config option
  • 90850d3 decrement attempt on snooze, unaltered max_attempts (#730)
  • e296461 enable the reindexer by default, add NeverSchedule (#718)
  • 0e97c89 set "periodic": true in periodic job metadata (#728)
  • 0f09f80 Bump the go-dependencies group across 5 directories with 7 updates (#723)
  • bc29131 enable dependabot across all dirs (#719)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/riverqueue/river/riverdriver/riverpgxv5](https://github.com/riverqueue/river) from 0.14.1 to 0.16.0.
- [Release notes](https://github.com/riverqueue/river/releases)
- [Changelog](https://github.com/riverqueue/river/blob/master/CHANGELOG.md)
- [Commits](riverqueue/river@v0.14.1...v0.16.0)

---
updated-dependencies:
- dependency-name: github.com/riverqueue/river/riverdriver/riverpgxv5
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 3, 2025
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants