fix(deps): update river monorepo to v0.16.0 #60
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.15.0
->v0.16.0
v0.15.0
->v0.16.0
v0.15.0
->v0.16.0
Release Notes
riverqueue/river (github.com/riverqueue/river)
v0.16.0
Compare Source
Added
NeverSchedule
returns aPeriodicSchedule
that never runs. This can be used to effectively disable the reindexer or any other maintenance service. PR #718.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
andriver_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 theriver.Config
type viaReindexerSchedule
. Most installations will benefit from this process, but it can be disabled altogether usingNeverSchedule
. 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 themax_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 themax_attempts
value, and makes it simpler to implement aRetryPolicy
based on eitherattempt
ormax_attempts
. The number of snoozes is also tracked in the job's metadata assnoozes
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 onattempt - len(errors)
for some reason. PR #730.ByPeriod
uniqueness is now based off a job'sScheduledAt
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.
This PR was generated by Mend Renovate. View the repository job log.