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.14.0 #31

Merged
merged 1 commit into from
Nov 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 3, 2024

This PR contains the following updates:

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

Release Notes

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

v0.14.0

Compare Source

Added
  • Expose JobCancelError and JobSnoozeError types to more easily facilitate testing. PR #​665.
Changed
  • Tune the client to be more aggressive about fetching when it just fetched a full batch of jobs, or when it skipped its previous triggered fetch because it was already full. This should bring more consistent throughput to poll-only mode and in cases where there is a backlog of existing jobs but new ones aren't being actively inserted. This will result in increased fetch load on many installations, with the benefit of increased throughput. As before, FetchCooldown still limits how frequently these fetches can occur on each client and can be increased to reduce the amount of fetch querying. Thanks Chris Gaffney (@​gaffneyc) for the idea, initial implementation, and benchmarks. PR #​663.
Fixed
  • riverpgxv5 driver: Hijack() the underlying listener connection as soon as it is acquired from the pgxpool.Pool in order to prevent the pool from automatically closing it after it reaches its max age. A max lifetime makes sense in the context of a pool with many conns, but a long-lived listener does not need a max lifetime as long as it can ensure the conn remains healthy. PR #​661.

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.

Copy link
Contributor Author

renovate bot commented Nov 3, 2024

ℹ 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.13.0 -> v0.14.0
github.com/riverqueue/river/rivershared v0.13.0 -> v0.14.0

@renovate renovate bot added the dependencies update of dependent libraries label Nov 3, 2024
@github-actions github-actions bot removed the dependencies update of dependent libraries label Nov 3, 2024
Copy link

sonarqubecloud bot commented Nov 3, 2024

@golanglemonade golanglemonade merged commit 46c07b2 into main Nov 3, 2024
12 checks passed
@golanglemonade golanglemonade deleted the renovate/river-monorepo branch November 3, 2024 23:37
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