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

Update river monorepo to v0.15.0 #23

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 16, 2024

This PR contains the following updates:

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

Release Notes

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

v0.15.0

Compare Source

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.
  • Add missing doc for JobRow.UniqueStates + reveal rivertype.UniqueOptsByStateDefault() to provide access to the default set of unique job states. PR #​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.
  • 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.
  • Fewer slice allocations during unique insertions. PR #​705.
Fixed
  • Exponential backoffs at degenerately high job attempts (>= 310) no longer risk overflowing time.Duration. PR #​698.

v0.14.3

Compare Source

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

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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 Pull requests that update a dependency file label Dec 16, 2024
Copy link
Author

renovate bot commented Dec 16, 2024

ℹ Artifact update notice

File name: app/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):

  • 4 additional dependencies were updated

Details:

Package Change
github.com/jackc/pgx/v5 v5.7.1 -> v5.7.2
github.com/riverqueue/river/riverdriver v0.14.2 -> v0.15.0
github.com/riverqueue/river/rivershared v0.14.2 -> v0.15.0
golang.org/x/crypto v0.30.0 -> v0.31.0

@renovate renovate bot force-pushed the renovate/river-monorepo branch from 59c7632 to 37f2611 Compare December 27, 2024 14:54
@renovate renovate bot changed the title Update river monorepo to v0.14.3 Update river monorepo to v0.15.0 Dec 27, 2024
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