alexlebens/infrastructure
1
0
Fork 0
Code Issues 1 Pull Requests 7 Actions Packages Projects Releases Wiki Activity

Update slskd/slskd Docker tag to v0.23.1 #860

Merged
alexlebens merged 1 commits from renovate/slskd-slskd-0.x into main 2025-07-08 01:51:25 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2025-07-07 01:01:01 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
slskd/slskd (source) minor 0.22.5 -> 0.23.1

Release Notes

slskd/slskd (slskd/slskd)

v0.23.1

Compare Source

What's Changed

Full Changelog: https://github.com/slskd/slskd/compare/0.23.0...0.23.1

v0.23.0

Compare 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: https://github.com/slskd/slskd/compare/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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [slskd/slskd](https://slskd.org) ([source](https://github.com/slskd/slskd)) | minor | `0.22.5` -> `0.23.1` | --- ### Release Notes <details> <summary>slskd/slskd (slskd/slskd)</summary> ### [`v0.23.1`](https://github.com/slskd/slskd/releases/tag/0.23.1) [Compare Source](https://github.com/slskd/slskd/compare/0.23.0...0.23.1) #### What's Changed - Fix regression in scripts and webhooks causing json to be missing detail by [@&#8203;jpdillingham](https://github.com/jpdillingham) in https://github.com/slskd/slskd/pull/1389 **Full Changelog**: https://github.com/slskd/slskd/compare/0.23.0...0.23.1 ### [`v0.23.0`](https://github.com/slskd/slskd/releases/tag/0.23.0) [Compare Source](https://github.com/slskd/slskd/compare/0.22.5...0.23.0) ### 🎉 Database Migrations (that preserve data!) This release introduces a new system that performs database migrations on existing data ([#&#8203;1343](https://github.com/slskd/slskd/issues/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 [#&#8203;1291](https://github.com/slskd/slskd/issues/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](https://github.com/slskd/slskd/blob/master/docs/migrations.md), 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 - Add a system to perform database migrations by [@&#8203;jpdillingham](https://github.com/jpdillingham) in https://github.com/slskd/slskd/pull/1343 - Fix remaining transfter State queries using HasFlag() by [@&#8203;jpdillingham](https://github.com/jpdillingham) in https://github.com/slskd/slskd/pull/1356 - Extend health check startup to 60 minutes, set $SHELL for docker container, and bump the GC memory limit from 500MiB to 2GiB by [@&#8203;jpdillingham](https://github.com/jpdillingham) in https://github.com/slskd/slskd/pull/1359 - Bump Soulseek.NET to 7.1.0 by [@&#8203;jpdillingham](https://github.com/jpdillingham) in https://github.com/slskd/slskd/pull/1363 - Update documentation for scripts by [@&#8203;jpdillingham](https://github.com/jpdillingham) in https://github.com/slskd/slskd/pull/1384 - Bump http-proxy-middleware from 2.0.6 to 2.0.9 in /src/web by [@&#8203;dependabot](https://github.com/dependabot) in https://github.com/slskd/slskd/pull/1329 **Full Changelog**: https://github.com/slskd/slskd/compare/0.22.5...0.23.0 </details> --- ### 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 is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xLjMiLCJ1cGRhdGVkSW5WZXIiOiI0MS4xLjMiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImltYWdlIl19-->
renovate-bot added the
image
 label 2025-07-07 01:01:01 +00:00
renovate-bot added 1 commit 2025-07-07 01:01:02 +00:00
Update slskd/slskd Docker tag to v0.23.0
All checks were successful
lint-test-helm / helm-lint (pull_request) Successful in 21s
Details
renovate/stability-days Updates have met minimum release age requirement
Details
149ba2351c
renovate-bot force-pushed renovate/slskd-slskd-0.x from 149ba2351c to 1076662318 2025-07-07 07:03:25 +00:00 Compare
renovate-bot force-pushed renovate/slskd-slskd-0.x from 1076662318 to d19dd5557c 2025-07-07 09:03:38 +00:00 Compare
renovate-bot force-pushed renovate/slskd-slskd-0.x from d19dd5557c to e2e70f013b 2025-07-07 10:03:21 +00:00 Compare
renovate-bot force-pushed renovate/slskd-slskd-0.x from e2e70f013b to dc299dfee6 2025-07-07 17:04:04 +00:00 Compare
renovate-bot changed title from Update slskd/slskd Docker tag to v0.23.0 to Update slskd/slskd Docker tag to v0.23.1 2025-07-08 01:01:25 +00:00
renovate-bot force-pushed renovate/slskd-slskd-0.x from dc299dfee6 to 815bc945f2 2025-07-08 01:01:25 +00:00 Compare
alexlebens merged commit b5d66dc1d6 into main 2025-07-08 01:51:25 +00:00
alexlebens deleted branch renovate/slskd-slskd-0.x 2025-07-08 01:51:26 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Renovate
Issue generated by Renovate.
automerge
This PR will be automerged by Renovate.
chart
Chart update generated by Renovate.
image
Image update generated by Renovate.
stale
PR or Issue that has not been updated recently.
No Label
image
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gitea-bot renovate-bot alexlebens
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexlebens/infrastructure#860
No description provided.
Delete Branch "renovate/slskd-slskd-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?