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

fix(deps): update river monorepo to v0.16.0 #60

Merged
merged 1 commit into from
Feb 1, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 28, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/riverqueue/river v0.15.0 -> v0.16.0 age adoption passing confidence
github.com/riverqueue/river/riverdriver/riverpgxv5 v0.15.0 -> v0.16.0 age adoption passing confidence
github.com/riverqueue/river/rivertype v0.15.0 -> v0.16.0 age adoption passing confidence

Release Notes

riverqueue/river (github.com/riverqueue/river)

v0.16.0

Compare Source

Added
  • NeverSchedule returns a PeriodicSchedule that never runs. This can be used to effectively disable the reindexer or any other maintenance service. PR #​718.
  • Add SkipUnknownJobCheck client config option to skip job arg worker validation. PR #​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.

  • 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.

  • 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.

  • ByPeriod uniqueness is now based off a job's ScheduledAt instead of the current time if it has a value. PR #​734.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies update of dependent libraries label Jan 28, 2025
Copy link
Contributor Author

renovate bot commented Jan 28, 2025

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 2 additional dependencies were updated

Details:

Package Change
github.com/riverqueue/river/riverdriver v0.15.0 -> v0.16.0
github.com/riverqueue/river/rivershared v0.15.0 -> v0.16.0

@renovate renovate bot requested a review from a team as a code owner January 28, 2025 18:14
@github-actions github-actions bot removed the dependencies update of dependent libraries label Jan 28, 2025
@golanglemonade golanglemonade merged commit a0fee0f into main Feb 1, 2025
12 checks passed
@golanglemonade golanglemonade deleted the renovate/river-monorepo branch February 1, 2025 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant