chore(deps): update dependency slskd/slskd to v0.25.0 #6062

renovate-bot · 2026-04-19T06:03:48Z

renovate-bot commented

2026-04-19 06:03:48 +00:00

This PR contains the following updates:

Package	Update	Change
slskd/slskd (source)	minor	`0.24.5` → `0.25.0`

Release Notes

slskd/slskd (slskd/slskd)

`v0.25.0`

Compare Source

🎉 Big Release!

This release contains a number of mostly unrelated changes.

Licensing

I have added 'Additional Terms' to the AGPLv3 that clarify the conditions under which folks can distribute and modify slskd, which Section 7 of the AGPLv3 allows. These terms include preservation of notices and licenses (already required by the AGPLv3, the terms spell the requirements out explicitly), mandatory identification of modifications (again, already required), mandatory rebranding (renaming forks to something that won't be confused with slskd), and the mandatory modification of the client version supplied to the server at login.

The full text of these Additional Terms can be found at the bottom of the LICENSE in the root of the repository. I've also added a NOTICE in the hopes that folks will be drawn to it and see that the LICENSE includes Additional Terms, and I've added a FORKING.md that explains the new terms in plain English.

To explain why I've done this, I'll share an excerpt from FORKING.md:

The requirements exist for two reasons, and both are about the people who use the software.

The first is to make sure users always know they are using software licensed under the AGPL. That matters because the AGPL gives users meaningful rights: the right to know that the source code exists, the right to access it, and the right to understand what they are running. Those rights only mean something if users are actually informed of them. Requiring that the full LICENSE be included with every distribution, and that license notices be preserved everywhere they appear, ensures that no user ever ends up with a copy of this software that hides or obscures the terms under which it was released.

The second is to make sure users understand who made the software they are using. They should be able to tell where it came from, who maintains it, what has been changed and by whom, and whether it is the original project or a fork. A user who installs a fork deserves to know it is a fork. The requirements around naming, branding, source file headers, and identification notices all serve this goal. They are not intended to discourage forking — they are intended to make sure that anyone who uses a fork has an accurate picture of what they have.

With AI becoming mainstream it is now incredibly easy to fork a project and manipulate it in ways that are harmful to users and/or the server(s) the software connects to. This behavior, unfortunately, is permissible under the AGPLv3. All I can do is ensure that users aren't deceived into using these untrusted and potentially harmful forks.

Docker User/Permissions

The slskd Docker container now supports both Docker's built in --user/user: and now the Linuxserver/*arr style PUID/PGID methods for running the container as a specific user. The built-in method is objectively superior, but I noticed that people frequently got hung up on permissions because they were using PUID/PGID without understanding that it wasn't supported.

These methods are mutually exclusive; users must choose one or the other. Users should also be aware that when using the PUID/PGID method, the container will chown the mounted /app directory on startup. This may be unexpected, but it is the intended behavior. The chown isn't recursive; users will need to do that themselves if needed.

Examples in the README and Docker docs have been updated to reflect these changes. I welcome any feedback about the approach in the Dockerfile or contents of the docs.

Configuration May Be Broken

Users who have configured things under the global, groups, or integration keys in the configuration file will find that the app will log an error and exit early until they apply the necessary changes. This is unfortunate, but the alternative was to not do that and allow people to continue using the app without their configuration being respected.

Pull request #1704 outlines the changes and provides an example of what needs to be done by correcting the configuration docs. tl;dr:

Rename the global key to transfers
Move all limits keys so that they appear nested under the upload key of the associated group
Rename the integration key to integrations

These changes were made to make room for upcoming features (stay tuned!). The rename of the integration key was admittedly not necessary for that, but I figured I would sneak it in.

What's Changed

BREAKING: Move all transfer options under a 'transfers' key by @jpdillingham in #1672
Add errors for deprecated keys by @jpdillingham in #1698
Update docs to reflect config changes by @jpdillingham in #1704
Append Additional Terms to the AGPLv3 license by @jpdillingham in #1675
Adjust NOTICE indent, add license info to startup banner by @jpdillingham in #1690
Fix "Search Again" by @rfletcher in #1666
Fix bug causing an error when updating the config file while the app is running by @jpdillingham in #1682
fix favicon.ico relative path by @deepsweet in #1696
Add BatchId and Attempts to Transfers database, change migration naming scheme by @jpdillingham in #1670
Add the ability to specify base delay for exponential backoff, add onRetry delegate for Retry.Do by @jpdillingham in #1671
Interlock updates of shared scanner vars by @jpdillingham in #1687
Add support for PUID/PGID to Docker by @jpdillingham in #1695
Bump Soulseek.NET to 9.0.0, set minor version to 760 by @jpdillingham in #1674
Bump picomatch from 2.3.1 to 2.3.2 in /src/web by @dependabot[bot] in #1684
Bump flatted from 3.2.7 to 3.4.2 in /src/web by @dependabot[bot] in #1676
Bump yaml in /src/web by @dependabot[bot] in #1680
Bump Soulseek.NET to 10.0.0 by @jpdillingham in #1691
Bump lodash from 4.17.23 to 4.18.1 in /src/web by @dependabot[bot] in #1692
Bump lodash-es from 4.17.23 to 4.18.1 in /src/web by @dependabot[bot] in #1689
Upgrade to .NET 10 by @jpdillingham in #1693
Bump axios from 1.13.5 to 1.15.0 in /src/web by @dependabot[bot] in #1694

New Contributors

@rfletcher made their first contribution in #1666
@deepsweet made their first contribution in #1696

Full Changelog: https://github.com/slskd/slskd/compare/0.24.5...0.25.0

Configuration

📅 Schedule: (in timezone America/Chicago)

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 these updates 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.24.5` → `0.25.0` | --- ### Release Notes <details> <summary>slskd/slskd (slskd/slskd)</summary> ### [`v0.25.0`](https://github.com/slskd/slskd/releases/tag/0.25.0) [Compare Source](https://github.com/slskd/slskd/compare/0.24.5...0.25.0) ##### 🎉 Big Release! This release contains a number of mostly unrelated changes. ##### Licensing I have added 'Additional Terms' to the AGPLv3 that clarify the conditions under which folks can distribute and modify slskd, which Section 7 of the AGPLv3 allows. These terms include preservation of notices and licenses (already required by the AGPLv3, the terms spell the requirements out explicitly), mandatory identification of modifications (again, already required), mandatory rebranding (renaming forks to something that won't be confused with slskd), and the mandatory modification of the client version supplied to the server at login. The full text of these Additional Terms can be found at the bottom of the [LICENSE](https://github.com/slskd/slskd/blob/master/LICENSE) in the root of the repository. I've also added a [NOTICE](https://github.com/slskd/slskd/blob/master/NOTICE) in the hopes that folks will be drawn to it and see that the LICENSE includes Additional Terms, and I've added a [FORKING.md](https://github.com/slskd/slskd/blob/master/FORKING.md) that explains the new terms in plain English. To explain why I've done this, I'll share an excerpt from FORKING.md: > The requirements exist for two reasons, and both are about the people who use the software. > The first is to make sure users always know they are using software licensed under the AGPL. That matters because the AGPL gives users meaningful rights: the right to know that the source code exists, the right to access it, and the right to understand what they are running. Those rights only mean something if users are actually informed of them. Requiring that the full LICENSE be included with every distribution, and that license notices be preserved everywhere they appear, ensures that no user ever ends up with a copy of this software that hides or obscures the terms under which it was released. > The second is to make sure users understand who made the software they are using. They should be able to tell where it came from, who maintains it, what has been changed and by whom, and whether it is the original project or a fork. A user who installs a fork deserves to know it is a fork. The requirements around naming, branding, source file headers, and identification notices all serve this goal. They are not intended to discourage forking — they are intended to make sure that anyone who uses a fork has an accurate picture of what they have. With AI becoming mainstream it is now incredibly easy to fork a project and manipulate it in ways that are harmful to users and/or the server(s) the software connects to. This behavior, unfortunately, is permissible under the AGPLv3. All I can do is ensure that users aren't deceived into using these untrusted and potentially harmful forks. ##### Docker User/Permissions The slskd Docker container now supports both Docker's built in `--user`/`user:` and now the Linuxserver/\*arr style `PUID`/`PGID` methods for running the container as a specific user. The built-in method is objectively superior, but I noticed that people frequently got hung up on permissions because they were using `PUID`/`PGID` without understanding that it wasn't supported. These methods are mutually exclusive; users must choose one or the other. Users should also be aware that when using the `PUID`/`PGID` method, the container will `chown` the mounted `/app` directory on startup. This may be unexpected, but it is the intended behavior. The `chown` isn't recursive; users will need to do that themselves if needed. Examples in the [README](https://github.com/slskd/slskd/blob/master/README.md) and [Docker docs](https://github.com/slskd/slskd/blob/master/docs/docker.md) have been updated to reflect these changes. I welcome any feedback about the approach in the [Dockerfile](https://github.com/slskd/slskd/blob/master/Dockerfile#L106) or contents of the docs. ##### Configuration May Be Broken Users who have configured things under the `global`, `groups`, or `integration` keys in the configuration file will find that the app will log an error and exit early until they apply the necessary changes. This is unfortunate, but the alternative was to *not* do that and allow people to continue using the app without their configuration being respected. Pull request [#1704](https://github.com/slskd/slskd/issues/1704) outlines the changes and provides an example of what needs to be done by correcting the configuration docs. tl;dr: 1. Rename the `global` key to `transfers` 2. Move all limits keys so that they appear nested under the upload key of the associated group 3. Rename the `integration` key to `integrations` These changes were made to make room for upcoming features (stay tuned!). The rename of the integration key was admittedly not necessary for that, but I figured I would sneak it in. ##### What's Changed - BREAKING: Move all transfer options under a 'transfers' key by [@jpdillingham](https://github.com/jpdillingham) in [#1672](https://github.com/slskd/slskd/pull/1672) - Add errors for deprecated keys by [@jpdillingham](https://github.com/jpdillingham) in [#1698](https://github.com/slskd/slskd/pull/1698) - Update docs to reflect config changes by [@jpdillingham](https://github.com/jpdillingham) in [#1704](https://github.com/slskd/slskd/pull/1704) - Append Additional Terms to the AGPLv3 license by [@jpdillingham](https://github.com/jpdillingham) in [#1675](https://github.com/slskd/slskd/pull/1675) - Adjust NOTICE indent, add license info to startup banner by [@jpdillingham](https://github.com/jpdillingham) in [#1690](https://github.com/slskd/slskd/pull/1690) - Fix "Search Again" by [@rfletcher](https://github.com/rfletcher) in [#1666](https://github.com/slskd/slskd/pull/1666) - Fix bug causing an error when updating the config file while the app is running by [@jpdillingham](https://github.com/jpdillingham) in [#1682](https://github.com/slskd/slskd/pull/1682) - fix favicon.ico relative path by [@deepsweet](https://github.com/deepsweet) in [#1696](https://github.com/slskd/slskd/pull/1696) - Add BatchId and Attempts to Transfers database, change migration naming scheme by [@jpdillingham](https://github.com/jpdillingham) in [#1670](https://github.com/slskd/slskd/pull/1670) - Add the ability to specify base delay for exponential backoff, add onRetry delegate for Retry.Do by [@jpdillingham](https://github.com/jpdillingham) in [#1671](https://github.com/slskd/slskd/pull/1671) - Interlock updates of shared scanner vars by [@jpdillingham](https://github.com/jpdillingham) in [#1687](https://github.com/slskd/slskd/pull/1687) - Add support for PUID/PGID to Docker by [@jpdillingham](https://github.com/jpdillingham) in [#1695](https://github.com/slskd/slskd/pull/1695) - Bump Soulseek.NET to 9.0.0, set minor version to 760 by [@jpdillingham](https://github.com/jpdillingham) in [#1674](https://github.com/slskd/slskd/pull/1674) - Bump picomatch from 2.3.1 to 2.3.2 in /src/web by [@dependabot](https://github.com/dependabot)\[bot] in [#1684](https://github.com/slskd/slskd/pull/1684) - Bump flatted from 3.2.7 to 3.4.2 in /src/web by [@dependabot](https://github.com/dependabot)\[bot] in [#1676](https://github.com/slskd/slskd/pull/1676) - Bump yaml in /src/web by [@dependabot](https://github.com/dependabot)\[bot] in [#1680](https://github.com/slskd/slskd/pull/1680) - Bump Soulseek.NET to 10.0.0 by [@jpdillingham](https://github.com/jpdillingham) in [#1691](https://github.com/slskd/slskd/pull/1691) - Bump lodash from 4.17.23 to 4.18.1 in /src/web by [@dependabot](https://github.com/dependabot)\[bot] in [#1692](https://github.com/slskd/slskd/pull/1692) - Bump lodash-es from 4.17.23 to 4.18.1 in /src/web by [@dependabot](https://github.com/dependabot)\[bot] in [#1689](https://github.com/slskd/slskd/pull/1689) - Upgrade to .NET 10 by [@jpdillingham](https://github.com/jpdillingham) in [#1693](https://github.com/slskd/slskd/pull/1693) - Bump axios from 1.13.5 to 1.15.0 in /src/web by [@dependabot](https://github.com/dependabot)\[bot] in [#1694](https://github.com/slskd/slskd/pull/1694) ##### New Contributors - [@rfletcher](https://github.com/rfletcher) made their first contribution in [#1666](https://github.com/slskd/slskd/pull/1666) - [@deepsweet](https://github.com/deepsweet) made their first contribution in [#1696](https://github.com/slskd/slskd/pull/1696) **Full Changelog**: <https://github.com/slskd/slskd/compare/0.24.5...0.25.0> </details> --- ### Configuration 📅 **Schedule**: (in timezone America/Chicago) - 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 these updates again. --- - [ ] 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-bot added the docker label 2026-04-19 06:03:48 +00:00

renovate-bot added 1 commit 2026-04-19 15:54:52 +00:00

chore(deps): update dependency slskd/slskd to v0.25.0

lint-test-helm / lint-helm (pull_request) Successful in 57s

Details

lint-test-helm / validate-kubeconform (pull_request) Successful in 53s

Details

render-manifests / render-manifests (pull_request) Successful in 1m32s

Details

62227a6b95

renovate-bot force-pushed renovate/unified-slskd from 940f4c7a86 to 62227a6b95

2026-04-19 15:54:52 +00:00

Compare

alexlebens merged commit 3fa8ca84f3 into main

2026-04-19 15:57:59 +00:00

alexlebens referenced this issue from a commit

2026-04-19 15:58:00 +00:00

Merge pull request 'chore(deps): update dependency slskd/slskd to v0.25.0' (#6062) from renovate/unified-slskd into main

alexlebens deleted branch renovate/unified-slskd

2026-04-19 15:58:07 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: alexlebens/infrastructure#6062