Skip to content

Update updates-patch-minor#5219

Merged
stavros-k merged 4 commits into
masterfrom
renovate/updates-patch-minor
Jun 22, 2026
Merged

Update updates-patch-minor#5219
stavros-k merged 4 commits into
masterfrom
renovate/updates-patch-minor

Conversation

@truenasbot

@truenasbot truenasbot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
databasus/databasus minor v3.44.0 → v3.46.0
ghcr.io/slskd/slskd (source) minor 0.24.5 → 0.25.1
ghcr.io/windmill-labs/windmill minor 1.734.0 → 1.735.0
itzg/minecraft-bedrock-server patch 2026.6.0 → 2026.6.1

Release Notes

databasus/databasus (databasus/databasus)

v3.46.0

Compare Source

Changelog

[3.46.0] - 2026-06-20

✨ Features
  • mysql/mariadb: Make extended inserts and Galera wsrep_on=OFF optional (issues #​636, #​630, #​635) (38f5694)
  • postgresql: Add isSkipUserMappings to handle FDW user mapping (0a9b390)
🐛 Bug Fixes
  • verification image: Remove PGDG-unavailable extensions to unblock build (222557d)
  • logical: Mark backup Failed, not Canceled, when SaveFile fails (7366c20)
  • physical: Key WAL history rows on parent databases.id to fix cross-timeline PITR (issue #​643) (f93a6c3)
  • email: Add SMTP_INSECURE_SKIP_VERIFY for self-signed SMTP certs (issue #​624) (d37c3a7)
  • verification: Handle missing extensions during backup verification (issue #​619) (e0c7638)
  • storages: Stream unlimited-size S3 backups via chunked objects (issue #​617) (a107648)
🔨 Refactoring
  • agent: Drive verification-agent config flags from a binding registry (33ea9e7)
🐳 Docker
  • Image: databasus/databasus:v3.46.0
  • Platforms: linux/amd64, linux/arm64

v3.45.0

Compare Source

Changelog

[3.45.0] - 2026-06-18

✨ Features
  • helm: Add ServiceAccount and extraVolumes support for Pod Security Standards (issue #​614) (899a4a4)
🐛 Bug Fixes
  • verification: Decode renamed postgresqlLogical field in agent assignment (14845f8)
  • verification: Align agent DTO field with backend postgresqlLogical key (ba2bc06)
  • security: Harden runtime Docker image (issue #​613) (cbfbe76)
🐳 Docker
  • Image: databasus/databasus:v3.45.0
  • Platforms: linux/amd64, linux/arm64
slskd/slskd (ghcr.io/slskd/slskd)

v0.25.1

Compare Source

What's Changed

Full Changelog: slskd/slskd@0.25.0...0.25.1

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 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:

  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

New Contributors

Full Changelog: slskd/slskd@0.24.5...0.25.0

windmill-labs/windmill (ghcr.io/windmill-labs/windmill)

v1.735.0

Compare Source

Features
  • clarify session draft bar tracks all workspace draft changes (#​9714) (ed016a5)
  • copilot: improve global-mode path selection + add path-selection evals (#​9698) (74a2329)
  • link files & folders to the global AI chat (#​9520) (84cc043)
  • scope default instance db name to workspace (dt_/dl_) (#​9699) (4a8a724)
Bug Fixes
  • enforce job_dir containment when writing module files (#​9703) (e403f92)
  • frontend: deploy full script/flow draft from AI chat via shared module (#​9642) (23bf6bf)
  • frontend: strip raw-app post-deploy diff noise (raw_app/lock/data) (#​9706) (e20a277)
  • ignore NotFound errors when deleting log files from object store (#​9707) (8a0b0ab)
  • oauth: restore bring-your-own CC token URL override (#​9711) (ef4962e)
  • sanitize git credentials from ansible executor errors and logs (#​9697) (ace7b68)
itzg/docker-minecraft-bedrock-server (itzg/minecraft-bedrock-server)

v2026.6.1

Compare Source

What's Changed

Other Changes

Full Changelog: itzg/docker-minecraft-bedrock-server@2026.6.0...2026.6.1

Configuration

📅 Schedule: (UTC)

  • 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Mend Renovate.

@stavros-k stavros-k merged commit 7fa1c04 into master Jun 22, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@stavros-k stavros-k stavros-k approved these changes

Assignees

No one assigned

Labels

minor patch

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@truenasbot @stavros-k @bugclerk