chore(deps): update container image ghcr.io/bitmagnet-io/bitmagnet to v0.8.0@c638773 by renovate #21612
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:
0.7.14
->v0.8.0
Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
bitmagnet-io/bitmagnet (ghcr.io/bitmagnet-io/bitmagnet)
v0.8.0
Compare Source
Classifier reimplementation
The classifier has been re-implemented and now uses a DSL allowing for full customisation. Several bugs have also been fixed, and a preparatory database migration for search ordering has been added.
The classifier documentation can be found at https://bitmagnet.io/tutorials/classifier.html.
Build reimplementation
The build has been re-implemented using https://github.com/goreleaser/goreleaser, thanks to @KyleSanderson. A number of new platform-specific build artifacts are now available.
Seeders/Leechers bug
There has somehow been a bug present, since day 1, whereby seeders and leechers were being swapped by the DHT crawler! This is fixed in 0.8.x. The first beta included a migration that would fix existing data, but the query just takes too long (for larger indexes), and so it has been removed from the migration.
Until now, no-one noticed - but If you care and would like to fix this in your index, you can run the following query, replacing the time with the time at which you did the 0.8.x upgrade. Be warned, this query may take a while for larger indexes! In time, much of the data will naturally fix itself anyway as the S/L numbers get re-scraped by the crawler when the torrent is re-discovered.
What's Changed
New Contributors
Full Changelog: bitmagnet-io/bitmagnet@v0.7.14...v0.8.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 Renovate Bot.