chore(deps): update bitmagnet-io/bitmagnet docker tag to v0.9.4 #736
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.9.3
->v0.9.4
Release Notes
bitmagnet-io/bitmagnet (bitmagnet-io/bitmagnet)
v0.9.4
Compare Source
This release includes 2 optimizations that should reduce the load that queue jobs place on the database, including for the 0.9.0 upgrade job.
It should also reduce instances of
ERROR: canceling statement due to user request
in the Postgres logs, but note that Bitmagnet does cancel some database queries because it sometimes tries 2 query strategies in a race and cancels the slowest one, so this message doesn't indicate a problem.What's Changed
Full Changelog: bitmagnet-io/bitmagnet@v0.9.3...v0.9.4
Configuration
📅 Schedule: Branch creation - "after 3am on Sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.