Update updates-patch-minor#5203
Merged
Merged
Conversation
7ae8c41 to
8487312
Compare
stavros-k
approved these changes
Jun 19, 2026
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
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:
2026.6.0→2026.6.1v3.44.0→v3.45.0v1.0.34→v1.0.35v5.1.8→v5.1.92.9.13→2.9.142026.6.0→2026.6.1v2.0.3→v2.1.01.3.3-stable→1.4.0-stable0.24.2079→0.24.2080v0.29.0→v0.29.12.27.2→2.27.32.27.2→2.27.32.2.0-nvidia→2.3.0-nvidia2.2.0-noavx2→2.3.0-noavx22.2.0→2.3.00.72.4-rootless→v0.73.0-rootless0.72.4→v0.73.05.1.3→5.1.40.24.5→0.25.1v0.15.5→v0.16.92.12.0→2.13.00.74.4→0.74.60.74.4→0.74.61.729.0→1.732.01.0.6→1.0.730.0.4→30.2.40.72.4→0.73.02026.6.18-bd73cc09e→2026.6.19-fe1848673Release Notes
cloudflare/cloudflared (cloudflare/cloudflared)
v2026.6.1Compare Source
SHA256 Checksums:
databasus/databasus (databasus/databasus)
v3.45.0Compare Source
Changelog
[3.45.0] - 2026-06-18
✨ Features
🐛 Bug Fixes
🐳 Docker
databasus/databasus:v3.45.0amruthpillai/reactive-resume (ghcr.io/amruthpillai/reactive-resume)
v5.1.9Compare Source
Highlights
Resume Builder & Rendering
AI, MCP & Self-Hosting
FLAG_DISABLE_API_RATE_LIMITfor trusted self-hosted deployments that need to disable authentication API rate limiting, and documented it in the Docker self-hosting guide. #3149FLAG_SHOW_SPONSORS, sponsor assets, landing-page placement, docs navigation, and README sponsor information for Atlas Cloud. f14d8ce69Localization & Maintenance
Full Changelog: v5.1.8...v5.1.9
esphome/esphome (ghcr.io/esphome/esphome)
v2026.6.1Compare Source
esphome idedatawith the native ESP-IDF toolchain esphome#17040 by @swoboda1337getarcaneapp/arcane (ghcr.io/getarcaneapp/manager)
v2.1.0Compare Source
New features
CLI - New features
Bug fixes
CLI - Bug fixes
Dependencies
Other
Full Changelog: getarcaneapp/arcane@v2.0.3...v2.1.0
Jackett/Jackett (ghcr.io/home-operations/jackett)
v0.24.2080Compare Source
Changes:
ea383a6magnetcat: bump domainsThis list of changes was auto generated.
shlinkio/shlink (ghcr.io/shlinkio/shlink)
v5.1.4Compare Source
Added
Changed
Deprecated
Removed
Fixed
[3159] Connections using insecure transport are prohibitedwhenDB_USE_ENCRYPTION=trueagainst a server requiring TLS.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 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
stalwartlabs/stalwart (ghcr.io/stalwartlabs/stalwart)
v0.16.9Compare Source
[0.16.9] - 2026-06-15
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
Changed
Fixed
*/changesmethods leak ids of non-shared objects (reported by @5ud0er).http_headerfunction.defaultvirtual queue.address-dataare ignored.keepis not specified.Check binary attestation here
v0.16.8Compare Source
[0.16.8] - 2026-06-06
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
Changed
AES-256-GCM-SIVAEAD format that carries the account name for proxy routing.Fixed
550 Mailbox not found.FileNode/getreturns a stale state string.SieveSystemInterpreter.defaultReturnPathandMtaQueueQuota.matchoptional expressions.dns-update-v0.5.1.Check binary attestation here
v0.16.7Compare Source
[0.16.7] - 2026-05-28
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
spamtestin trusted Sieve scripts.Changed
Fixed
TXTrecords when updating RRSet.Keep-Aliveis enabled.Check binary attestation here
v0.16.6Compare Source
[0.16.6] - 2026-05-20
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
orcpt.Changed
$or{prefixes as secure secrets.Fixed
acl-principal-prop-setREPORT enforced the wrong privilege.Thread/getdid not filter by per-mailbox ACLs on shared accounts.UID FETCH N:*could miss messages moved into a SELECTed mailbox by another connection.v=spf1 a -allrecords for apex domains.TXTrecords when they exceed 255 characters.defaultCertificateIdwhen renewing a certificate that is currently set as default.DNS-01authorizations sequentially to avoid race conditions in some DNS providers.replaceaction adds an extraFromheader.Check binary attestation here
v0.16.5Compare Source
[0.16.5] - 2026-05-11
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
is_ip_in_cidrexpression function for CIDR matching.Changed
mail-authto 0.9 (which bumpshickory-resolverto 0.26).hickory.Fixed
nullvalues fails.Failedinstead ofErrorwhen the query returns no results.EAFNOSUPPORTerror..well-knownendpoints.RCPTbefore rewriting.dns-updatecrate):MXandSRVrecords.subnamefor apex records instead of@, which the API rejects.TXTrecord content in double quotes (RFC 1035) to suppress dashboard warnings.calcardcrate):STATUS:CANCELLEDmapping fromVTODOto JSCalendar.PT0S.Check binary attestation here
v0.16.4Compare Source
[0.16.4] - 2026-05-05
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
Changed
Fixed
AccountSettingsobject returninvalidProperties.mail-parserpanic with certain messages containing corrupted attachments.RCPTon checks.AddressBook/queryfetches wrong resources.%EMAILADDRESS%when no email address is provided.Check binary attestation here
v0.16.3Compare Source
[0.16.3] - 2026-04-30
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
Changed
STALWART_HTTPS_PORTwithSTALWART_PUBLIC_URL.app_instead ofappto avoid issues with some clients that do not support spaces in passwords.Fixed
INFO.Check binary attestation here
v0.16.2Compare Source
[0.16.2] - 2026-04-28
If you are upgrading from v0.16.x, replace the binary (or run
docker pull). If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.Added
userinfoendpoint when JWT token does not contain an email claim.verifyAfterWriteoption to verify that objects have persisted after writing.Changed
Fixed
credentialIdwhen there are password changes.Check binary attestation here
v0.16.1Compare Source
[0.16.1] - 2026-04-25
This version includes multiple breaking changes. If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
Added
system('node_hostname')andsystem('node_role')expression variables to retrieve the local node hostname and cluster role respectively.Changed
Fixed
receivedAtheaders after importing (#2939).receivedAtheaders.BINARYfetch responses (#2940).CAArecord updates.Check binary attestation here
v0.16.0Compare Source
[0.16.0] - 2026-04-20
This version includes multiple breaking changes. If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
Added
zxcvbnalgorithmMX,TXT,CNAME,SRV,CAAandTLSArecords (#463 #1017 #1419 #2438 #1370 #1406 #1371)TLSArecords when ACME certificates change (#1664)SIG(0)support (#856)DNS-PERSIST-01ACME challenge support (#2837)CAArecord support (#468) withaccounturiparameter (#1933)TLSArecords publishing restricted to3 1 1and2 1 1(#2193)aud) claim (#2603) and scope validation support.Changed
smtp,imapandmemorydirectory backends.aws-lcfor cryptographic operations instead ofring.rustls-platform-verifierfor TLS certificate verification instead ofwebpki(#247).Fixed
Go aheadtextinMailboxOtherThanquery logic.hasAttachmentsearch field (#2778)8000bytesRIGHTScapability (#2762)ACL SETpermission override.304NOT_MODIFIEDonIf-None-MatchPUTrequests if they are equal to the existing ones.idsorteable.204CORS preflight responsesCheck binary attestation here
Stirling-Tools/Stirling-PDF (ghcr.io/stirling-tools/stirling-pdf)
v2.13.0: 2.13.0 MCP, files UI tweaks and bug fixesCompare Source
This release contains some cool updates but mostly backend enabler work for features to come as well as enabling us to redeploy our online https://stirling.com/app back to a familiar UI.
This release also contains:
And bug fixes for:
What's Changed
Bug Fixes (please note most of these are related to SaaS not OSS product, we will be making the separation in notes clearer in next release)
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate.