feat(container): update ghcr.io/slskd/slskd ( 0.24.5 → 0.25.1 ) - autoclosed#11004
Merged
feat(container): update ghcr.io/slskd/slskd ( 0.24.5 → 0.25.1 ) - autoclosed#11004
Conversation
| datasource | package | from | to | | ---------- | ------------------- | ------ | ------ | | docker | ghcr.io/slskd/slskd | 0.24.5 | 0.25.1 |
Contributor
Author
--- kubernetes/apps/downloads/slskd/app Kustomization: downloads/slskd HelmRelease: downloads/slskd
+++ kubernetes/apps/downloads/slskd/app Kustomization: downloads/slskd HelmRelease: downloads/slskd
@@ -45,13 +45,13 @@
SLSKD_SLSK_LISTEN_PORT: 50300
envFrom:
- secretRef:
name: slskd
image:
repository: ghcr.io/slskd/slskd
- tag: 0.24.5@sha256:17ef977563be206f3b5932080b1e23883b2cb39dc9010640f6f39b4eaec887e3
+ tag: 0.25.1@sha256:ab9ed50e028b524cefdb7c1dd8ebca368a076e18441ee8ac2326473eb850b4c3
probes:
liveness:
custom: true
enabled: true
spec:
failureThreshold: 3 |
Contributor
Author
--- HelmRelease: downloads/slskd StatefulSet: downloads/slskd
+++ HelmRelease: downloads/slskd StatefulSet: downloads/slskd
@@ -59,13 +59,13 @@
value: 'true'
- name: SLSKD_SLSK_LISTEN_PORT
value: '50300'
envFrom:
- secretRef:
name: slskd
- image: ghcr.io/slskd/slskd:0.24.5@sha256:17ef977563be206f3b5932080b1e23883b2cb39dc9010640f6f39b4eaec887e3
+ image: ghcr.io/slskd/slskd:0.25.1@sha256:ab9ed50e028b524cefdb7c1dd8ebca368a076e18441ee8ac2326473eb850b4c3
livenessProbe:
failureThreshold: 3
httpGet:
path: /health
port: 5030
initialDelaySeconds: 0 |
lovenet-renovate-operator
Bot
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.24.5→0.25.1Release Notes
slskd/slskd (ghcr.io/slskd/slskd)
v0.25.1Compare Source
What's Changed
Full Changelog: slskd/slskd@0.25.0...0.25.1
v0.25.0Compare 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:
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 stylePUID/PGIDmethods 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 usingPUID/PGIDwithout 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/PGIDmethod, the container willchownthe mounted/appdirectory on startup. This may be unexpected, but it is the intended behavior. Thechownisn'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, orintegrationkeys 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:
globalkey totransfersintegrationkey tointegrationsThese 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
New Contributors
Full Changelog: slskd/slskd@0.24.5...0.25.0
Configuration
📅 Schedule: (in timezone America/New_York)
🚦 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 Mend Renovate.