feat(container): update ghcr.io/slskd/slskd ( 0.22.5 → 0.23.0 ) #2915
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![home-gitops-bot[bot]](https://avatars.githubusercontent.com/u/946892?s=60&v=4){kind=small}
home-gitops-bot
bot
added
renovate/container
type/minor
area/kubernetes
Deploying kubernetes-schemas with
|
| Latest commit: |
a199b73
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4f214380.kubernetes-schemas-5e0.pages.dev |
| Branch Preview URL: | https://renovate-ghcr-io-slskd-slskd.kubernetes-schemas-5e0.pages.dev |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.22.5->0.23.0Release Notes
slskd/slskd (ghcr.io/slskd/slskd)
v0.23.0Compare Source
🎉 Database Migrations (that preserve data!)
This release introduces a new system that performs database migrations on existing data (#1343), which was necessary to migrate the Transfers database to correct an out of memory issue at startup for users with a large number of transfer records (see #1291).
Upon first start after upgrading to 0.23.0 the application will apply the initial migration to the Transfers database (
transfers.db), if there is one. Depending on the system and the amount of data present, this may take a while, and the UI will be inaccessible during the process.Backups of existing databases are taken prior to the start of the process (you can find them in
/data/backups) and they aren't deleted automatically, so your historical data is safe. A feature to add auto deletion after a period of time will come later.In the unlikely event that the process fails to complete successfully, follow the directions in the new migration docs, which explain what to do if something goes wrong, and how to get the application back to a working state if the migration can't be completed.
If you find that your database can't be migrated successfully, please file an issue and I can work on providing a standalone migration tool.
What's Changed
Full Changelog: slskd/slskd@0.22.5...0.23.0
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 has been generated by Renovate Bot.