Security fix release for Coolify 4.3. Apply it with: curl -fsSL https://cdn.coollabs.io/coolify/patch.sh | sudo bash

Security

• Updated PHP to 8.4.27 to fix PHP2Shell (CVE-2026-109618, CVE-2026-109619).
• Updated Node.js to 24.22.1 for the terminal server and the asset build.
• Updated cloudflared to 2026.10.3
• Updated Sentinel to 1.1.2.

The Asterisk Development Team would like to announce
the release of Certified asterisk-22.8-cert5.

The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/certified-22.8-cert5
and
https://downloads.asterisk.org/pub/telephony/certified-asterisk

Repository: https://github.com/asterisk/asterisk
Tag: certified-22.8-cert5

This release resolves issues reported by the community
and would have not been possible without your participation.

Thank You!

Change Log for Release asterisk-certified-22.8-cert5

Links:

• Full ChangeLog
• GitHub Diff
• Tarball
• Downloads

Summary:

• Commits: 1
• Commit Authors: 1
• Issues Resolved: 1
• Security Advisories Resolved: 0

The Asterisk Development Team would like to announce
the release of Certified asterisk-20.7-cert12.

The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/certified-20.7-cert12
and
https://downloads.asterisk.org/pub/telephony/certified-asterisk

Repository: https://github.com/asterisk/asterisk
Tag: certified-20.7-cert12

This release resolves issues reported by the community
and would have not been possible without your participation.

Thank You!

Change Log for Release asterisk-certified-20.7-cert12

Links:

• Full ChangeLog
• GitHub Diff
• Tarball
• Downloads

Summary:

• Commits: 14
• Commit Authors: 4
• Issues Resolved: 8
• Security Advisories Resolved: 0

[0.16.27] - 2026-10-18

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

• IMAP:
  • APPEND and COPY/MOVE into another account's mailbox do not change the JMAP EmailDelivery state.
  • SEARCH RETURN with MIN or MAX alongside ALL returns only the minimum and maximum in ALL, and SAVE combined with MIN or MAX and ALL or COUNT saves only the minimum and maximum instead of every match.
• iTIP: Merging a received update does not copy the VTIMEZONE definitions it carries, so an occurrence moved by an external organizer can reference a TZID (for example W. Europe Standard Time) the stored event no longer defines, and Apple Calendar shows both the original and the moved occurrence.
• OAuth: Loopback redirect URIs without a path (for example http://127.0.0.1:45678) are not matched against registered loopback URIs on any port and are rejected by dynamic client registration.
• WebDAV: PROPFIND allprop returns DAV:current-user-principal, so Windows Explorer shows every file and folder under the account name.

Check binary attestation here

The PostgreSQL Global Development Group announces that the first release candidate of PostgreSQL 19 is now available for download. As a release candidate, PostgreSQL 19 RC 1 will be mostly identical to the initial release of PostgreSQL 19, though some more fixes may be applied prior to the general availability of PostgreSQL 19.

The next scheduled update release for supported versions of PostgreSQL, on November 12, 2026, will include a large number of fixes. Because of this, the release team decided to include these fixes in PostgreSQL 19 before its general availability. This means a second release candidate, PostgreSQL 19 RC 2, will be available on the same day as the update release.

The planned date for the general availability of PostgreSQL 19 is November 19, 2026. Please see the "Release Schedule" section for more details.

Upgrading to PostgreSQL 19 RC 1

To upgrade to PostgreSQL 19 RC 1 from earlier versions of PostgreSQL, you will need to use a major version upgrade strategy, e.g. pg_upgrade or pg_dump / pg_restore. For more information, please visit the documentation section on upgrading:

https://www.postgresql.org/docs/19/upgrading.html

Changes Since 19 Beta 4

Several bug fixes were applied to PostgreSQL 19 during the Beta 4 period. These include:

• Several fixes for REPACK (CONCURRENTLY).
• Several fixes for pg_plan_advice.
• Several fixes for new query planner optimizations that rely on whether an expression can be NULL.
• Several fixes for the automatic enablement of logical replication when wal_level is set to replica.
• Fix postgres_fdw statistics import to run as the owner of the foreign table instead of the user running ANALYZE.
• Several fixes for parallel autovacuum.
• Fix COPY (query) TO ... (FORMAT json) to use the query's column names, including aliases, as the JSON keys instead of the table's column names.

For a detailed list of fixes, please visit the open items page.

Release Schedule

This is the first release candidate for PostgreSQL 19. The release team plans to issue a second release candidate, PostgreSQL 19 RC 2, on November 12, 2026. Unless an issue is discovered that requires a delay or an additional release candidate, PostgreSQL 19 should be made generally available on November 19, 2026.

For further information please see the Beta Testing page.

Links

• Download
• Beta Testing Information
• PostgreSQL 19 Beta Release Notes
• PostgreSQL 19 Open Issues
• Submit a Bug
• Donate

If you have corrections or suggestions for this release announcement, please send them to the pgsql-www@lists.postgresql.org public mailing list.

njs-1.0.2 version has been released, with fixes for memory exhaustion vulnerability when parsing malformed XML (CVE-2026-101025), and inconsistent XML attribute values affecting signed XML validation (CVE-2026-101019).

nginx-1.30.6 stable and nginx-1.31.7 mainline versions have been released, with fixes for buffer overflow vulnerability when using alias with rewrite (CVE-2026-15176), buffer overflow vulnerability when evaluating string expressions with variables (CVE-2026-93479), request body injection vulnerability in HTTP/3 (CVE-2026-95101), session forgery vulnerability when using TLS session ticket key rotation (CVE-2026-97629), and use-after-free vulnerability when using ngx_http_ssi_module with AIO (CVE-2026-97205).

📦 Downloads available at

• https://user.bitfocus.io/download

💵 Donate to the project at

• open collective https://opencollective.com/companion

Companion v5.1.0 - Release Notes

📣 CORE FEATURES AND IMPROVEMENTS

• Graphics improvements

  • pinned properties for quicker access to commonly used properties in the style editor #4324 (#4442)
  • wysiwyg toolbar for basic edits to a button's style (#4341)
  • better custom preview aspect ratios (#4450)
  • surface gauge leds (#4314)
  • show expression value previews for elements and style overrides
  • add fill width setting and alpha support for fill colors #4359
  • allow value feedbacks as layered-button style overrides (#4379)
  • make button preview aspect entry more robust and more flexible
  • text style properties (#4337)
  • smooth text autosizing
  • support corner radius for box elements #4359
  • allow rotating composite elements

• Misc UX

  • rework button grid interactions (#4434)
  • support alt+click on CollapsibleTree nodes to expand all at that level
  • make split panel layouts resizable #2781
  • Show local variable value when collapsed (#4386)
  • configurable default export format #4349
  • make module deprecation more visible to users (#4495)

• APIs

  • Prototype of new full system REST API (#4259)
  • REST API to list surfaces and set brightness (#4405)
  • REST API token management (#4453)

• Expressions

  • new maths functions (#4388)
  • expression oscillator function (#4328)

• Variables

  • Local Variables on pages (#4332)
  • expose $(this:delta) for rotary actions and carry rotation amount (#4387)

• Controls

  • reference/mirror control type (#4339)
  • linked presets (#4284)

• Misc

  • lazily evaluate internal feedbacks that are children of an action (#4378)
  • Add milliseconds to log entries #2891
  • add COMPANION_INSTALL_NAME env var to set the installation name
  • prometheus metrics for monitoring (#4304)
  • streaming json parsing/generation (#4390)
  • report collection-disabled connections as disabled, add connection collection status variables #4479
  • add 'Surface: When connected' feedback #4124
  • randomInt() is not re-evaluated in Trigger conditions #3297
  • Add duration to press and release internal action #3389
  • add $(internal:date_monthname) variable #3819

🐞 BUG FIXES

• module versions refresh button not indicating progress
• keep unicode glyphs together when breaking a line #3671
• rework line breaking to work as is was long ago (#4372)
• font size scaling not always consider whether topbar is visible
• keep preset definition ids stable across re-conversion
• surface page-change defer condition and rescanUsb error reporting
• propagate image import errors #4438
• better report import progress to the ui
• sort to the connection selection dropdown (#4402)
• backup file renaming failing #4394
• try to ensure module are shutdown cleanly when companion exits
• adjust line draw bounds to not hide the line #4359
• measure font ascent/descent for better positioning #4359
• avoid excessive button-drawn events upon a cache hit
• colors when downscaling oversampled images
• dropdown freezing when selecting from a large list #4494
• expose pressed state to surfaces
• don't recreate desktop shortcut when updating
• static-text fields should not show expression toggles
• draw a placeholder for missing or cyclic composite elements
• update bonjour lib to limit query answer rate #4499
• logging stopping entirely after a non-string message is logged #4509

Full Changelog: v5.0.7...v5.1.0

[0.16.26] - 2026-10-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

• sd_notify support.
• JMAP: Mailbox/set allows moving a mailbox under a parent that already has a child with the same name, and rejects renames that only change the case of a mailbox name with alreadyExists.

Changed

Fixed

• DNSSEC: Use hickory-resolver patched fork at https://github.com/stalwartlabs/hickory-dns.
• RocksDB: Blob garbage collection rewrites every stored blob on each compaction of the blobs column family, about once per 128MB of new mail.
• Milter: End-of-headers is not sent to milters that negotiate SMFIP_NOHDRS without SMFIP_NOEOH, so the transaction stalls until it times out.
• OIDC: When the access token lacks the claimUsername claim but has an email claim, the account is built from email without consulting the userinfo endpoint.
• JMAP:
  • onSuccessUpdateEmail and onSuccessDestroyEmail entries in EmailSubmission/set that name an existing submission by id update or destroy the Email with the same id instead of the submission's own Email.
  • A VacationResponse/set that only sets isEnabled on an account without a vacation response activates an empty Sieve script.

Check binary attestation here

Fixes

• Fixed self-hosted startup failures caused by an incompatible PHP base image by pinning it to a stable version (#12141).

Full Changelog: v4.4.5...v4.4.6

Fixes

• Removed the 5 GB free disk space requirement that blocked manual and automatic updates.

Full Changelog: v4.4.4...v4.4.5

Features

• Added optional Cloudflare proxy mode for new DNS records.
• Added support for public IPv4 and IPv6 addresses in Git repository URLs.

Fixes

• Fixed IPv6 server addresses across connections, URLs, routing, and Hetzner provisioning.
• Fixed IPv6 connections to public database TCP proxies on IPv6-enabled networks (#12133).
• Fixed database proxy connections after database IP addresses changed.
• Prevented duplicate database environment variables and preserved source values when cloning applications. Removed existing duplicate Redis username and Nixpacks Node version entries.
• Fixed database startup so configuration files were written before containers started.
• Preserved application, database, service, and proxy containers during Docker cleanup.
• Fixed detection of legacy Compose containers for custom start commands and status updates.
• Restored valid Compose network names with required and alternative variable expressions (#12126).
• Fixed Infisical secret references that reached containers without expansion (#12128).
• Fixed S3 database and volume backup uploads on hosts with split DNS (#12129).
• Fixed custom DNS queries by retrying truncated UDP responses over TCP (#12076).
• Fixed GitHub App installation after switching teams and showed clear verification errors (#12122).
• Prevented duplicate upgrades and fixed stalled upgrade progress.
• Prevented configuration and route cache corruption during startup (#12120).
• Matched the Railpack build frontend version to the helper's installed CLI.
• Removed forced HTTP/1.1 for Git repository imports (PR #12080, #11579).
• Fixed resource name alignment when descriptions were empty (#12127).

Improvements

• Added a 5 GB free-space check before upgrades, with cleanup controls and a manual override. Automatic upgrades were skipped with a notification when space was low.
• Updated the sidebar user menu and toggle icon.

What's Changed

• revert(git): stop forcing HTTP/1.1 for repository imports by @peaklabs-dev in #12080

Full Changelog: v4.4.3...v4.4.4

Fixes and improvements

General

• fix dropping UDP packets during connection close (#6278) UDP packets were dropped in case of errors regardless of their size. Now they are dropped only if they are empty and there's an error.
• docs: fix youtube rtmps URL (#6286) The rtmps URL for Youtube was wrong. The fingerprint is not required anymore.
• prevent free access to playback server in case of legacy credentials (#6311) When legacy credentials are in use (readUser, readPass, publishUser, publishPass), access to the playback server is granted to anyone. Prevent this by granting access only to users using readUser, readPass.
• auth: skip JWKS fetch when no JWT is provided (#6274) authenticateJWT fetched the JWKS before checking whether the request carried a token at all. Every anonymous request, such as the first unauthenticatedRTSP DESCRIBE or HLS request that precedes a 401, caused an outbound request to the JWKS server while holding the manager's write lock. An unauthenticated client could therefore make the server contact the identity provider at will and, while that endpoint was slow or unreachable, stall JWT authentication for everybody. Return "JWT not provided" before touching the JWKS. Also check the JWKS response status code. A non-2xx reply was fed straight to the JSON decoder, so an error page surfaced as a confusing parse error,and an error reply that happened to hold valid JSON was cached as the key set for an hour. Reject it with the status code, as authenticateHTTP already does. Behavior for requests that carry a token against a healthy JWKS server is unchanged.
• rewindablereader: fix possible OOM (bluenviron/mediacommon#383) empty datagram packets might cause the allocation of unnecessary entries. Fix that.
• h264: revert bluenviron/mediacommon#142 (bluenviron/mediacommon#384) supporting standalone SEI units should not be necessary anymore since these are filtered out at the root (bluenviron/gortsplib#1184). In case of any issue that should arise after this change, open a bug report and we'll adjust things accordingly.
• h264: support SEI recovery point in DTS extractor (bluenviron/mediacommon#341) Treat a SEI recovery point message (payload type 6) as a random access point, similarly to a CRA in H265, so the DTS extractor can (re)initialize its state from the first coded frame that follows the recovery point.

API

• fix race condition when kicking RTSP sessions (#6260) (#6275)
• do not change passwords when their value is "" (#6141) (https://github.com/bluenviron/mediamtx/issues/6287) (#6292) some users call /config/global/get and passits content to /config/global/patch. Since the former now redacts passwords and replaces their value with "", this string is used as an effective password, breaking authentication. Now password values equal to "" are ignored by /config/global/patch, and the original password value is kept unchanged.
• fix deadlock when reloading the API (#6280) (#6279) (#6310) When the API is closing, a /config endpoint might be waiting on the server to reply, but the server is busy waiting on all API endpoints to return, causing a deadlock. Fix this by canceling requests from API endpoints to the server when the API is closing.

Media-Over-QUIC

• use "catalog" as catalog track name (#6268) Previously, the catalog track name was ".catalog" which is non-standard.

RTSP

• stop forwarding in case of read errors (#6266)
• apply path-level rtspUDPReadBufferSize to the first connection (#6291) The RTSP static source built its client before reading the path-level rtspUDPReadBufferSize, so the value only reached the client after a reconnection. Compute it before creating the client, as the MPEG-TS and RTP sources do and as this source did before #5488.
• server: change error return code of some methods (bluenviron/gortsplib#1091) (bluenviron/gortsplib#1174)
• drop standalone H264/H265 trailing SEIs (bluenviron/gortsplib#1184) #3614 bluenviron/mediacommon#142 #6257 bluenviron/mediacommon#382 H264/H265 access units containing a single SEI only, trailing other units, generated by someTP-Link/Tapo cameras, are non-standard and cause several issues in downstream components, including the DTS extractor and the recorder. Previously, the H265 DTS extractor was adjusted to support such units (bluenviron/gortsplib#142) but the problem represented itself with H265. Filter these units out at the root.
• make all decoders return at least 1 byte (bluenviron/gortsplib#1185)
• complete RTP/JPEG implementation (bluenviron/gortsplib#1187) add support for restart headers, limit support to JPEG types 0 and 1.

RTMP

• detect read errors even when the server is writing (#6267) Until now we relied exclusively on write errors to detect broken RTMP connections. Now read errors are checked too.
• make rawmessage.Write thread-safe (bluenviron/gortmplib#136)
• writer: drain inbound messages (#5776) (bluenviron/gortmplib#132) Some servers periodically send messages even when we're publishing. If they are not read, they fill an internal connectionbuffer and cause periodic disconnections. Now the Writer also drains inbound messages.
• reader: support FLV video command frames and skip empty audio messages (bluenviron/gortmplib#128) Someservers (e.g. Wowza Streaming Engine) send a video info/command frame before the first frame: a 2-byte message with frame type 5 and a single command byte (start of seek / end of seek). Video.unmarshal rejected it on length, aborting the whole connection. Add Video.FrameType (key frame, inter frame, command) and Video.Command, deprecate Video.IsKeyFrame in favour of FrameType, and skip command frames in Reader since they carry no data. Some servers (e.g. Wowza Streaming Engine) send an audio message with an empty bodybefore the first frame. allocateMessage rejected it with "not enough bytes", aborting the whole connection. Parse an empty body into an Audio with Codec = 0 and no other field, marshal it back to an empty body, and skip such messages in Reader since they carry no data, like FFmpeg does.
• rename message.Video.Type into message.Video.PacketType (bluenviron/gortmplib#138) This is to avoid confusion with the new message.Video.FrameType field.

HLS

• muxer: keep EXT-X-MAP in delta updates (bluenviron/gohlslib#397) Delta updates were generated without EXT-X-MAP, although all tags that are not skipped must remain in them. Apple clients stop playback (MoofManifold -16046) at the first delta update that skips a segment after delta updates without skipped segments.

WebRTC

• fix panic with specially-crafted WHEP requests (#6301) (#6309) this happened in case of WHEP requests with no media descriptions in the SDP.

Dependencies

• Go updated from 1.26 to 1.27
• code.cloudfoundry.org/bytefmt updated from v0.90.0 to v0.92.0
• github.com/bluenviron/gohlslib/v2 updated from v2.4.5 to v2.4.6
• github.com/bluenviron/gortmplib updated from v1.0.3 to v1.0.4
• github.com/bluenviron/gortsplib/v5 updated from v5.6.6 to v5.6.7
• github.com/bluenviron/mediacommon/v2 updated from v2.9.5 to v2.9.6
• github.com/datarhei/gosrt updated from v0.11.1-0.20260812091715-a77b40bb4b76 to v0.12.0
• github.com/gin-contrib/pprof updated from v1.5.5 to v1.5.6
• github.com/go-git/go-billy/v5 updated from v5.9.1 to v5.9.2
• github.com/go-git/go-git/v5 updated from v5.19.2 to v5.19.3
• github.com/pion/ice/v4 updated from v4.4.2 to v4.4.5
• github.com/pion/interceptor updated from v0.1.48 to v0.1.49
• github.com/pion/rtcp updated from v1.2.17 to v1.2.19
• github.com/pion/transport/v4 removed
• github.com/pion/webrtc/v4 updated from v4.2.20 to v4.2.22
• github.com/quic-go/quic-go updated from v0.62.0 to v0.63.0
• github.com/pion/datachannel updated from v1.6.2 to v1.6.3
• github.com/pion/dtls/v3 updated from v3.1.8 to v3.1.9
• github.com/pion/mdns/v2 updated from v2.2.0 to v2.2.2
• github.com/pion/sctp updated from v1.11.1 to v1.11.3
• github.com/pion/srtp/v3 updated from v3.0.15 to v3.1.3
• github.com/pion/stun/v4 updated from v4.0.0 to v4.0.1
• github.com/pion/turn/v5 updated from v5.1.0 to v5.1.2
• github.com/pjbgf/sha1cd updated from v0.6.0 to v0.7.0
• github.com/pion/transport/v5 v5.1.1 added

Security

Binaries are compiled from source code by the Release workflow, which is a fully-visible process that prevents any change or external interference in produced artifacts.

Checksums of binaries are also published in a public blockchain by using GitHub Attestations, and they can be verified by running:

ls mediamtx_* | xargs -L1 gh attestation verify --repo bluenviron/mediamtx

You can verify checksums of binaries by downloading checksums.sha256 and running:

cat checksums.sha256 | grep "$(ls mediamtx_*)" | sha256sum --check

Fixes

• Fixed static-site pull request previews that failed with a missing Dockerfile error. (#8238)
• Fixed the empty terminal container picker for resources with multiple containers. (#12110)
• Fixed nested Base64 custom labels in API updates and deployments. (PR #11473, #11435)
• Prevented DNS polling from filling the queue with duplicate file-sync jobs and delaying DNS checks and deployments. (#12098)
• Fixed the runtime log viewer failing to load with invalid saved filters. (#12101)
• Fixed missing Caddy traffic analytics after enabling analytics and redeploying applications with managed labels. (#12117)
• Preserved previously recorded commit messages when redeployments skipped cloning the repository. (#12116)
• Fixed card title alignment when descriptions were empty. (#12102)

Improvements

• Removed the truncated page-search hint from the navigation search button.
• Made dropdown controls more compact.
• Updated default example repository URLs in development mode to use the main branch.
• Added AMD64 and ARM64 development images from release branches, with versioned and commit-specific tags.

What's Changed

• fix(applications): normalize nested base64 custom labels by @andrasbacsai in #11473

Full Changelog: v4.4.2...v4.4.3

The Asterisk Development Team would like to announce
release candidate 2 of asterisk-24.0.0.

The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/24.0.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk

Repository: https://github.com/asterisk/asterisk
Tag: 24.0.0-rc2

This release resolves issues reported by the community
and would have not been possible without your participation.

Thank You!

Change Log for Release asterisk-24.0.0-rc2

Links:

• Full ChangeLog
• GitHub Diff
• Tarball
• Downloads

Summary:

• Commits: 3
• Commit Authors: 2
• Issues Resolved: 3
• Security Advisories Resolved: 0

User Notes:

Upgrade Notes:

Developer Notes:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling

  ast_channel_fd_add() now returns -1 if it fails to allocate
  space for the descriptor.

Commit Authors:

• Joshua C. Colp: (2)
• Mike Bradeen: (1)

Issue and Commit Detail:

Closed Issues:

• #2134: [bug]: Bridging channels which have been spied on with ChanSpy fails
• #2179: [bug]: No initial NOTIFY for dialog subscriptions when hint references CustomPresence without AstDB entry (regression in 22.11.0)
• #2186: [bug]: dialog-info NOTIFY for ringing extension no longer contains identity (caller ID) since 22.11.0

Commits By Author:

• Joshua C. Colp (2):

  • extstate/pjsip: Handle lack of or late loading of presence state.
  • extstate: Include causing device channel details in legacy callbacks.

• Mike Bradeen (1):

  • Audiohooks: Fix whisper framehook timer leak and masquerade handling

Commit List:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling
• extstate/pjsip: Handle lack of or late loading of presence state.
• extstate: Include causing device channel details in legacy callbacks.

Commit Details:

Audiohooks: Fix whisper framehook timer leak and masquerade handling
Author: Mike Bradeen
Date: 2026-09-25

Resolves several issues with the framehook added to allow whispering without
an underlying stream.

The timer is now owned by the audiohook list rather than the framehook. It is
retired on both channels during a masquerade and recreated when the audiohook(s)
are moved.

If the timer cannot be started, whisper audio is still mixed into the outbound
media as it was previously (requiring an underlying stream.)

An audiohook that cannot be moved to the new channel is now left DONE so that
its owner does not wait on it forever.

Resolves: #2134

DeveloperNote: ast_channel_fd_add() now returns -1 if it fails to allocate
space for the descriptor.

extstate/pjsip: Handle lack of or late loading of presence state.
Author: Joshua C. Colp
Date: 2026-09-25

The extension state implementation is stateful resulting in state
not being updated if a presence state provider does not publish an
update after loading. To handle providers which don't do this we
query for updated state if we are asked for it and the existing
state is invalid. This ensures that if the presence state provider
is loaded later we will get the updated state when asked.

The func_presencestate module is written to publish the persisted
custom presence states at load time. This failed for entries with
a not_set state as this resulted in querying the presence provider
that was not yet registered. The provider is now registered before
this ensuring the update can be published.

This change also fixes an issue in PJSIP where a SUBSCRIBE for a
hint that had an invalid presence state configuration would not
send an initial NOTIFY. We now treat an invalid presence state as
not set instead.

Fixes: #2179

extstate: Include causing device channel details in legacy callbacks.
Author: Joshua C. Colp
Date: 2026-09-29

When a legacy extension state callback registers it can optionally
do so in a way that it will receive the channel(s) that have caused
a device to ring. This is used in PJSIP for the dialog-info+xml
support so that phones can display who is calling the monitored
extension.

An issue was introduced in the extension state rewrite where this
did not occur for the actual device that caused the extension state
update. It was only being done for additional devices that could be
involved. This has been fixed so that it is now done for the causing
device.

Fixes: #2186

The Asterisk Development Team would like to announce
release candidate 2 of asterisk-23.6.0.

The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/23.6.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk

Repository: https://github.com/asterisk/asterisk
Tag: 23.6.0-rc2

This release resolves issues reported by the community
and would have not been possible without your participation.

Thank You!

Change Log for Release asterisk-23.6.0-rc2

Links:

• Full ChangeLog
• GitHub Diff
• Tarball
• Downloads

Summary:

• Commits: 3
• Commit Authors: 2
• Issues Resolved: 3
• Security Advisories Resolved: 0

User Notes:

Upgrade Notes:

Developer Notes:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling

  ast_channel_fd_add() now returns -1 if it fails to allocate
  space for the descriptor.

Commit Authors:

• Joshua C. Colp: (2)
• Mike Bradeen: (1)

Issue and Commit Detail:

Closed Issues:

• #2134: [bug]: Bridging channels which have been spied on with ChanSpy fails
• #2179: [bug]: No initial NOTIFY for dialog subscriptions when hint references CustomPresence without AstDB entry (regression in 22.11.0)
• #2186: [bug]: dialog-info NOTIFY for ringing extension no longer contains identity (caller ID) since 22.11.0

Commits By Author:

• Joshua C. Colp (2):

  • extstate/pjsip: Handle lack of or late loading of presence state.
  • extstate: Include causing device channel details in legacy callbacks.

• Mike Bradeen (1):

  • Audiohooks: Fix whisper framehook timer leak and masquerade handling

Commit List:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling
• extstate/pjsip: Handle lack of or late loading of presence state.
• extstate: Include causing device channel details in legacy callbacks.

Commit Details:

Audiohooks: Fix whisper framehook timer leak and masquerade handling
Author: Mike Bradeen
Date: 2026-09-25

Resolves several issues with the framehook added to allow whispering without
an underlying stream.

The timer is now owned by the audiohook list rather than the framehook. It is
retired on both channels during a masquerade and recreated when the audiohook(s)
are moved.

If the timer cannot be started, whisper audio is still mixed into the outbound
media as it was previously (requiring an underlying stream.)

An audiohook that cannot be moved to the new channel is now left DONE so that
its owner does not wait on it forever.

Resolves: #2134

DeveloperNote: ast_channel_fd_add() now returns -1 if it fails to allocate
space for the descriptor.

extstate/pjsip: Handle lack of or late loading of presence state.
Author: Joshua C. Colp
Date: 2026-09-25

The extension state implementation is stateful resulting in state
not being updated if a presence state provider does not publish an
update after loading. To handle providers which don't do this we
query for updated state if we are asked for it and the existing
state is invalid. This ensures that if the presence state provider
is loaded later we will get the updated state when asked.

The func_presencestate module is written to publish the persisted
custom presence states at load time. This failed for entries with
a not_set state as this resulted in querying the presence provider
that was not yet registered. The provider is now registered before
this ensuring the update can be published.

This change also fixes an issue in PJSIP where a SUBSCRIBE for a
hint that had an invalid presence state configuration would not
send an initial NOTIFY. We now treat an invalid presence state as
not set instead.

Fixes: #2179

extstate: Include causing device channel details in legacy callbacks.
Author: Joshua C. Colp
Date: 2026-09-29

When a legacy extension state callback registers it can optionally
do so in a way that it will receive the channel(s) that have caused
a device to ring. This is used in PJSIP for the dialog-info+xml
support so that phones can display who is calling the monitored
extension.

An issue was introduced in the extension state rewrite where this
did not occur for the actual device that caused the extension state
update. It was only being done for additional devices that could be
involved. This has been fixed so that it is now done for the causing
device.

Fixes: #2186

The Asterisk Development Team would like to announce
release candidate 2 of asterisk-22.12.0.

The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/22.12.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk

Repository: https://github.com/asterisk/asterisk
Tag: 22.12.0-rc2

This release resolves issues reported by the community
and would have not been possible without your participation.

Thank You!

Change Log for Release asterisk-22.12.0-rc2

Links:

• Full ChangeLog
• GitHub Diff
• Tarball
• Downloads

Summary:

• Commits: 3
• Commit Authors: 2
• Issues Resolved: 3
• Security Advisories Resolved: 0

User Notes:

Upgrade Notes:

Developer Notes:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling

  ast_channel_fd_add() now returns -1 if it fails to allocate
  space for the descriptor.

Commit Authors:

• Joshua C. Colp: (2)
• Mike Bradeen: (1)

Issue and Commit Detail:

Closed Issues:

• #2134: [bug]: Bridging channels which have been spied on with ChanSpy fails
• #2179: [bug]: No initial NOTIFY for dialog subscriptions when hint references CustomPresence without AstDB entry (regression in 22.11.0)
• #2186: [bug]: dialog-info NOTIFY for ringing extension no longer contains identity (caller ID) since 22.11.0

Commits By Author:

• Joshua C. Colp (2):

  • extstate/pjsip: Handle lack of or late loading of presence state.
  • extstate: Include causing device channel details in legacy callbacks.

• Mike Bradeen (1):

  • Audiohooks: Fix whisper framehook timer leak and masquerade handling

Commit List:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling
• extstate/pjsip: Handle lack of or late loading of presence state.
• extstate: Include causing device channel details in legacy callbacks.

Commit Details:

Audiohooks: Fix whisper framehook timer leak and masquerade handling
Author: Mike Bradeen
Date: 2026-09-25

Resolves several issues with the framehook added to allow whispering without
an underlying stream.

The timer is now owned by the audiohook list rather than the framehook. It is
retired on both channels during a masquerade and recreated when the audiohook(s)
are moved.

If the timer cannot be started, whisper audio is still mixed into the outbound
media as it was previously (requiring an underlying stream.)

An audiohook that cannot be moved to the new channel is now left DONE so that
its owner does not wait on it forever.

Resolves: #2134

DeveloperNote: ast_channel_fd_add() now returns -1 if it fails to allocate
space for the descriptor.

extstate/pjsip: Handle lack of or late loading of presence state.
Author: Joshua C. Colp
Date: 2026-09-25

The extension state implementation is stateful resulting in state
not being updated if a presence state provider does not publish an
update after loading. To handle providers which don't do this we
query for updated state if we are asked for it and the existing
state is invalid. This ensures that if the presence state provider
is loaded later we will get the updated state when asked.

The func_presencestate module is written to publish the persisted
custom presence states at load time. This failed for entries with
a not_set state as this resulted in querying the presence provider
that was not yet registered. The provider is now registered before
this ensuring the update can be published.

This change also fixes an issue in PJSIP where a SUBSCRIBE for a
hint that had an invalid presence state configuration would not
send an initial NOTIFY. We now treat an invalid presence state as
not set instead.

Fixes: #2179

extstate: Include causing device channel details in legacy callbacks.
Author: Joshua C. Colp
Date: 2026-09-29

When a legacy extension state callback registers it can optionally
do so in a way that it will receive the channel(s) that have caused
a device to ring. This is used in PJSIP for the dialog-info+xml
support so that phones can display who is calling the monitored
extension.

An issue was introduced in the extension state rewrite where this
did not occur for the actual device that caused the extension state
update. It was only being done for additional devices that could be
involved. This has been fixed so that it is now done for the causing
device.

Fixes: #2186

The Asterisk Development Team would like to announce
release candidate 2 of asterisk-20.22.0.

The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/20.22.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk

Repository: https://github.com/asterisk/asterisk
Tag: 20.22.0-rc2

This release resolves issues reported by the community
and would have not been possible without your participation.

Thank You!

Change Log for Release asterisk-20.22.0-rc2

Links:

• Full ChangeLog
• GitHub Diff
• Tarball
• Downloads

Summary:

• Commits: 3
• Commit Authors: 2
• Issues Resolved: 3
• Security Advisories Resolved: 0

User Notes:

Upgrade Notes:

Developer Notes:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling

  ast_channel_fd_add() now returns -1 if it fails to allocate
  space for the descriptor.

Commit Authors:

• Joshua C. Colp: (2)
• Mike Bradeen: (1)

Issue and Commit Detail:

Closed Issues:

• #2134: [bug]: Bridging channels which have been spied on with ChanSpy fails
• #2179: [bug]: No initial NOTIFY for dialog subscriptions when hint references CustomPresence without AstDB entry (regression in 22.11.0)
• #2186: [bug]: dialog-info NOTIFY for ringing extension no longer contains identity (caller ID) since 22.11.0

Commits By Author:

• Joshua C. Colp (2):

  • extstate/pjsip: Handle lack of or late loading of presence state.
  • extstate: Include causing device channel details in legacy callbacks.

• Mike Bradeen (1):

  • Audiohooks: Fix whisper framehook timer leak and masquerade handling

Commit List:

• Audiohooks: Fix whisper framehook timer leak and masquerade handling
• extstate/pjsip: Handle lack of or late loading of presence state.
• extstate: Include causing device channel details in legacy callbacks.

Commit Details:

Audiohooks: Fix whisper framehook timer leak and masquerade handling
Author: Mike Bradeen
Date: 2026-09-25

Resolves several issues with the framehook added to allow whispering without
an underlying stream.

The timer is now owned by the audiohook list rather than the framehook. It is
retired on both channels during a masquerade and recreated when the audiohook(s)
are moved.

If the timer cannot be started, whisper audio is still mixed into the outbound
media as it was previously (requiring an underlying stream.)

An audiohook that cannot be moved to the new channel is now left DONE so that
its owner does not wait on it forever.

Resolves: #2134

DeveloperNote: ast_channel_fd_add() now returns -1 if it fails to allocate
space for the descriptor.

extstate/pjsip: Handle lack of or late loading of presence state.
Author: Joshua C. Colp
Date: 2026-09-25

The extension state implementation is stateful resulting in state
not being updated if a presence state provider does not publish an
update after loading. To handle providers which don't do this we
query for updated state if we are asked for it and the existing
state is invalid. This ensures that if the presence state provider
is loaded later we will get the updated state when asked.

The func_presencestate module is written to publish the persisted
custom presence states at load time. This failed for entries with
a not_set state as this resulted in querying the presence provider
that was not yet registered. The provider is now registered before
this ensuring the update can be published.

This change also fixes an issue in PJSIP where a SUBSCRIBE for a
hint that had an invalid presence state configuration would not
send an initial NOTIFY. We now treat an invalid presence state as
not set instead.

Fixes: #2179

extstate: Include causing device channel details in legacy callbacks.
Author: Joshua C. Colp
Date: 2026-09-29

When a legacy extension state callback registers it can optionally
do so in a way that it will receive the channel(s) that have caused
a device to ring. This is used in PJSIP for the dialog-info+xml
support so that phones can display who is calling the monitored
extension.

An issue was introduced in the extension state rewrite where this
did not occur for the actual device that caused the extension state
update. It was only being done for additional devices that could be
involved. This has been fixed so that it is now done for the causing
device.

Fixes: #2186

Features

• Added settings search to the command palette, with Global and This page scopes. (#12111)
• Added GitHub Actions runner support for servers used for both deployments and builds, with shared-resource warnings. (#12109)
• Added per-server controls to store full, anonymized, or no client IP addresses in traffic analytics through the UI and API.
• Added Cloudflare Tunnel updates from server settings, with progress logs and a background restart.

Fixes

• Fixed unnecessary Docker build cache resets caused by temporary build helper containers. (#11781; closed #11387 and #11525)
• Fixed deployment of large Docker Compose files, including Sentry self-hosted, with many YAML aliases or build arguments without values. (Closed #11725)
• Fixed the traffic globe not appearing when country data arrived after the initial load. (#12108)
• Fixed traffic path rows for different domains and combined overflow entries into one Other paths row.
• Prevented Chrome local network permission prompts caused by favicons for private network hosts. (#12107)
• Increased the Cloudflare Tunnel startup timeout and stored new tunnel configurations outside temporary directories.
• Prevented duplicate form updates.

Improvements

• Made searchable and multi-select dropdowns consistent across forms.

What's Changed

• fix(domains): skip favicons for private network hosts by @andrasbacsai in #12107
• fix(traffic): show geo globe when country data becomes available by @andrasbacsai in #12108
• feat(github-runners): support deployment and build servers by @andrasbacsai in #12109
• feat(search): add settings search to the command palette by @andrasbacsai in #12111
• fix(deploy): keep build helper containers out of --add-host by @brandonrbridges in #11781

New Contributors

• @brandonrbridges made their first contribution in #11781

Full Changelog: v4.4.1...v4.4.2

Features

• Added volume backup success, failure, and warning notifications through team backup notification channels.
• Added configurable alerts for missing volume backups in the UI and API, with alerts disabled by default.

Fixes

• Fixed deployment progress checks that stayed active after missing queue jobs exceeded the deployment timeout.
• Included running scheduled tasks and database and volume backups in progress checks.
• Fixed the log viewer when its parent component refreshed.
• Recorded database and volume backups that missed their scheduled start as failed and sent failure notifications.
• Fixed Telegram topic routing for backup warnings, missing volume backups, and volume recovery failures.
• Set database sessions to UTC to prevent timestamp offsets.

Improvements

• Added SCHEDULED_JOBS_DISPATCH_MODE to select sequential or concurrent schedule dispatch. Self-hosted instances used sequential dispatch by default to reduce CPU and memory use; cloud instances kept concurrent dispatch.
• Updated Sentinel to 1.0.2 and pinned the Sentinel host image to a fixed digest.

Full Changelog: v4.4.0...v4.4.1

This release adds built in traffic analytics for Traefik and Caddy, experimental support for SQLite as a database, readable container names with a configurable container prefix, third-party secret managers, Cloudflare DNS management, OpenID Connect sign-in, GitHub Actions runners on build servers, and Docker registry logins. It also includes many fixes.

Added

• Traffic analytics for Traefik and Caddy using the new Rust version of sentinel (#11292)
  • Sentinel ingests the proxies JSON access logs and stores aggregate rollups only. Raw access logs are rotated on the server.
  • Per-server toggle on the new server Analytics page, off by default. Enabling it restarts the proxy and Sentinel. Optional MaxMind license key; GeoIP works without one.
  • Views: team dashboard widget, global Analytics page with server and application filters, per-server Analytics page, per-application and per-service Analytics tab.
  • Metrics: requests, bandwidth, unique visitors, and p95 latency KPIs with sparklines, requests chart, status-code breakdown, interactive globe with country breakdown, device, path, host, referrer, and browser breakdowns, optional live refresh for the 24h range.
  • Settings for top-N, sampling threshold, retention, and GeoIP. Nginx is out of scope.
  • Caddy applications and services need a redeploy after the toggle changes so their logging labels are updated. Caddy needs caddy-docker-proxy 2.9 or newer.

• SQLite database (#11992)
  • Add SQLite as a standalone database, based on a custom image (peakimages/sqlite).
  • Connect a SQLite database to an application or Docker Compose application on the same server in one click. Coolify mounts its data volume, protects connected volumes, and lets you unlink applications.
  • Back up and restore SQLite databases, including scheduled backups.

• Container name prefix for generated names (#11704)

  • Optional prefix for the generated (rolling update) naming mode, set in the application's container settings or via custom_container_name_prefix in the API. It is slugified, limited to 30 characters, and unique per server. Rolling updates keep working compared to the custom container name (consistent mode) which loses rolling updates.

  	before	after
  single container app (prefix: shop-api)	k9p2m4x7q1w3e5r6t8y0u2i4-20260908T141530	shop-api-20260908T141530
  compose service web (prefix: shop-api)	web-k9p2m4x7q1w3e5r6t8y0u2i4-20260908T141530	web-shop-api-20260908T141530

• Split action buttons (#11409)

  • Resource action menus show the primary action as a one-click button with secondary actions in a dropdown. This improves UX as the primary action is now only one click away, rather than two clicks and hidden inside a dropdown menu

• Autofocus on auth forms (#11324)

• Third-party secret managers (#11474)

  • Doppler, Infisical, and HashiCorp Vault as secret sources for applications, services, and standalone databases.
  • {{vault.KEY}} references are resolved during deployment and database start. Values are never stored in Coolify's database and are redacted from deployment logs.
  • Key browsing, bulk import as references, autocomplete, provider validation, and clear deployment errors for missing secrets. Build reuse is skipped when build-time secret references may have changed.

• Team audit log (#11462, #11788)

  • Searchable, filterable log of UI, API, MCP, and webhook activity under Team → Audit Log, covering resource changes, deployments, backups, proxy controls, membership, token, and integration changes, account security events, and server, application, service, and instance settings.
  • Entries show the previous and new value of each changed field under "View changes". Changes are encrypted at rest, and secrets, commands, and configuration content are left out.
  • Stores actor, resource, and request context with sensitive metadata redacted. Events are pruned after 90 days.
  • Team admins and owners can read events with GET /audit-events in the API.

• Database import API (#11699)

  • Import backups into standalone and service databases from an upload, a server path, or S3 storage: POST /databases/{uuid}/imports/uploads, POST /databases/{uuid}/imports, GET /databases/{uuid}/imports/{activity_id}, and the same under /services/{uuid}/databases/{database_uuid}/imports.
  • Uploading and starting an import need the write permission. An import from a server path also needs deploy.

• Cloudflare integration tokens (#11359)

• Cloudflare DNS record management (#11699)

  • From the application and service Domains pages, Coolify matches hostnames to zones reachable with the team's Cloudflare tokens and creates records pointing at the server.
  • Detects records that already point elsewhere and offers a replace action, shows a "Managed by Coolify" badge, and deletes managed records with the domain after confirmation.

• OpenID Connect single sign-on (#10543)

  • Sign in and register with any OIDC provider.
  • Registration policy per provider: allow or block password registration and user creation, optionally auto-join new users to the Root team.
  • Linked SSO identities are shown on the user profile. Provider-managed email addresses cannot be changed in Coolify.
  • Microsoft Entra ID: use https://login.microsoftonline.com/<tenant ID>/v2.0 as the issuer URL and add the optional ID token claims email and xms_edov to the app registration. xms_edov counts as a verified email.

• Alpine Linux server support (#6189)

  • Add and update alpine based servers with apk.

• Copy environment variable values (#11379)

  • Copy resolved values directly from the environment variables page. Shared variables and $SERVICE_* references resolve to their actual value, except references to locked shared variables. Locked variables have no copy button.

• Named volumes (#7591)

  • New volume mounts use named Docker volumes instead of host source paths, including on Swarm. New volumes are pre-filled with a resource-based name.
  • Existing bind mounts keep their source paths, which are shown read-only.

• Server roles for deployments and builds

  • Set a server to Deployments only, Builds only, or Deployments and builds in the server settings or via server_role in the API. The deprecated is_build_server field still works.
  • Deployments only servers never build images themselves, and applications on them need a Docker image name.
  • Choose per team whether builds fall back to the deployment server when no build server is usable.

• GitHub Actions self-hosted runners (beta) (#12054)

  • Builds only servers can run GitHub Actions workflow jobs for an organization GitHub App. Each job gets a new runner container that is removed when the job ends.
  • Set labels, parallel runners, CPU and memory limits, the runner image, timeouts, and Docker in jobs (privileged Docker-in-Docker, Sysbox, or none) on the new server GitHub Runners page. The host Docker socket is never mounted.
  • Jobs started by pull requests are refused unless you allow them.
  • The server role cannot be changed while runners are enabled, and a server can be reserved for runners so it takes no application builds.

• Docker registry logins (#12048)

  • The new Registries page and the Registries tab of each server list the registries a server is logged in to and the registries its applications need.
  • Log in, update, and log out with presets for Docker Hub, GHCR, GitLab, Google Artifact Registry, Azure ACR, and AWS ECR, or any other registry. Coolify runs docker login on the server and does not store the token.
  • API: GET /servers/{uuid}/registries, POST /servers/{uuid}/registries, POST /servers/{uuid}/registries/{registry}/check, and DELETE /servers/{uuid}/registries/{registry}.

• Docker images page (#11689)

  • The new server Images page lists every image with its size, age, and the containers that use it, and shows the total and reclaimable disk space. Unused images can be deleted after typing their reference.

• Traefik ACME certificates (#12015)

  • View and delete certificates stored in Traefik's acme.json on the new TLS Certificates page in the server's Proxy menu. Deleting does not revoke the certificate, and the server shows that the proxy needs a restart.
  • Coolify backs up acme.json before every change and keeps the last 10 backups, which can be restored or deleted on the same page.

• Account deletion (#12088)

  • Delete your own account from the profile page. Teams where you are the only member are deleted, you are removed from all other teams, and your API tokens and sessions are revoked.
  • Deletion is blocked for the root user, while a team you own alone still has servers, projects, or Git sources, and while a shared team would be left without an admin or owner.

• Preview deployments API

  • GET /applications/{uuid}/previews and GET /applications/{uuid}/previews/{pull_request_id} return preview deployments. POST /applications/{uuid}/previews opens or redeploys the preview of a pull request and needs the deploy permission.

• Reopen the live deployment log (#11783)

  • Services, databases, and applications show a "Deploying… View log" indicator that reopens the running log. Deploy, Start, or Restart during a running operation reopens the log instead of failing.

• Application settings filter (#11783)

  • Filter the application settings sidebar, including sub-pages such as Advanced → Proxy.

• Use variables such as ${NETWORK:-coolify} or ${COMPOSE_PROJECT_NAME}_default in Compose network names of applications and services, including a service's networks: list. A network name that is a single variable is added as an editable environment variable.

• Delete a server from its cloud provider (Hetzner, Vultr, or DigitalOcean) through the API with delete_from_provider=true on DELETE /servers/{uuid}. (#12026)

• Give additional users access to the Horizon dashboard with the HORIZON_ALLOWED_EMAILS environment variable (#9354)

• Show pending team invitations on the dashboard.

• Test S3 storages that were marked unusable again every hour, so they become usable on their own once the connection works.

• Generate a random manual webhook secret with one click.

• Show a warning icon on the server Proxy menu when the proxy is not running.

• Link the Healthcheck row in the status summary of applications and databases to the healthcheck page.

• Add a favicon, an Apple touch icon, and a web app manifest.

• Add OAuth settings to auto-join new OAuth users to the root team and to disable password registration while OAuth is on. The login page then shows "Only OAuth registration is enabled."

• Add a shared copy component which is used across resource (#11368)

Changed

• Realtime runs on Laravel Reverb inside the Coolify container, next to the terminal server. The separate coolify-realtime (Soketi) container is no longer used; existing proxy routes and port settings keep working, and a soketi override in docker-compose.custom.yml is still accepted. (#10530, #11935)
• Generated container names use an ISO 8601 timestamp suffix (<uuid>-20260908T141530) instead of HHMMSS plus microseconds (the old suffix is still recognized). (#11702)
• Containers are labelled with coolify.applicationUuid, coolify.serviceUuid, coolify.service.subUuid, and coolify.databaseUuid instead of numeric ID labels. Existing containers keep working and get the new labels on the next deploy or restart.
• Database restores: the import command is read-only, and single-database PostgreSQL restores no longer drop existing objects by default. The new "Replace objects that already exist" option (replace_existing in the API) restores the previous --clean behavior. PostgreSQL archive restores also skip owners and privileges unless "Keep owners and privileges" (keep_owners) is set. (#11699)
• Database restores support PostgreSQL custom and tar archives, MongoDB archives and dump directories, and bz2, xz, and zip files. All-databases MySQL and MariaDB restores can restore users and privileges (restore_mysql_users), and SQLite restores can pick the target file (sqlite_database). The import form shows the exact restore script.
• All OAuth providers are managed from one Settings → Authentication page with provider icons and clearer login buttons. (#10543)
• OAuth accounts link to a provider identity, not only to an email. The first OAuth login links the account. To link an existing account, the provider must verify the email, except for accounts without a password that an OAuth login made before this release. New accounts follow the registration settings.
• Each account links to one OAuth provider. If you used two providers with the same email before, use the first one you sign in with after the upgrade.
• If you rename a self-hosted GitLab, Authentik, Clerk, or Zitadel host, or change the Azure tenant, run php artisan oauth:rekey <provider> --from=<old URL or tenant> so linked accounts keep working.
• Authentik 2025.10 and later: to link an existing Coolify account to Authentik, the email scope must return email_verified: true. Add a scope mapping in Authentik under Customization → Property Mappings that returns {"email": request.user.email, "email_verified": True}, and use it on the provider instead of the default email mapping.
• OAuth logins ask for the 2FA code if 2FA is on, and SSO users can turn on 2FA without a password.
• Users with a linked OAuth identity confirm destructive actions with the typed confirmation only, without a password.
• The Google "Hosted domain" setting is enforced. * allows any Workspace account.
• Denied OAuth logins show the reason on the login page instead of a generic error.
• Metrics collection settings (collection rate, history retention, push interval) moved from the Sentinel page to the Charts page. The Sentinel custom image is saved with an Apply and restart button instead of autosave. (#11292)
• Chart tooltips show the viewer's local time and UTC. (#11292)
• The container log viewer has Time, Type, and Message columns, and log lines expand with pretty-printed JSON (#11292). Only the visible rows are rendered, so large logs stay responsive.
• Standalone database starts run through a queued job so credentials from secret managers can be resolved. (#11474)
• On new KeyDB and Dragonfly databases, a REDIS_PASSWORD environment variable sets the server password and the connection URLs. Databases created before this release keep their stored password unless the variable reads a secret manager.
• New proxy configurations use Traefik v3.7 and caddy-docker-proxy 2.13.
• Coolify no longer reconnects the proxy to all Docker networks every hour and on server checks. The proxy is connected when a destination is created, when an application or service is deployed, and when the proxy starts or restarts.
• Environment variable names must match [A-Za-z_][A-Za-z0-9_.]*. Existing runtime-only variables with other names, such as my-var, still deploy with a warning and a suggested name, while invalid build-time names stop image builds. (#11917)
• Applications on multiple servers: additional servers must use the same proxy (Traefik or Caddy) as the primary server and always pull the image the primary server pushed instead of building it. Persistent volumes and Docker Compose applications can no longer be combined with multiple servers. Existing setups get a warning in the deployment log. (#12053)
• Scheduled database backups, scheduled tasks, volume backups, and Docker cleanups are each dispatched every minute by their own scheduler process instead of one queued job, so a busy queue or a slow schedule type no longer delays the others.
• Stopping or deleting a resource runs Docker cleanup only when the server's disk usage is at or above its cleanup threshold and no cleanup finished in the last hour. Only one cleanup runs per server at a time.
• Hourly Sentinel version checks and weekly server patch checks run at a different time for each server instead of for all servers at once.
• High disk usage notifications repeat at most once per interval for each server, 24 hours by default instead of about hourly. Set the interval in Server → Advanced or with server_disk_usage_notification_interval_hours in the API. A new alert is sent earlier when usage dropped at least 5 points below the threshold and rises again.
• Logging in no longer accepts a pending team invitation automatically. Invitations are accepted on the invitation page.
• SSH_COMMAND_TIMEOUT=0 or an invalid value no longer removes the time limit of remote commands. The default of 3600 seconds is used instead.
• Docker Swarm can only be enabled for teams that already use it.
• Resource settings sidebars collapse their groups again, with the group of the active page open. (#11783)
• Production and preview environment variables are shown in separate labelled sections. (#11783)
• Project cards and lists show compact resource stats, the server list shows resource count and status, and database URLs have a copy button. (#11783)
• Notification channel toggles and database and service actions update instantly. (#11783)
• The running deployments indicator moved from a floating button into the sidebar (the top bar on mobile) and is also shown on the dashboard.
• The remaining native browser confirmation dialogs are replaced with Coolify confirmation modals.

Security

• Issue short-lived terminal session tokens on the server instead of sending SSH commands through the browser (#11942)
• Require the two-factor challenge for OAuth sign-in, link existing accounts only when the provider verified the email address, and enforce the configured Google Workspace domain (#11907, #11989)
• Build email verification links and the default OAuth callback URL from the instance URL instead of the request's Host header
• Remove the unused PUT /user/profile-information route, which changed the account email without verification
• Validate Git-based Docker Compose applications against Compose injection when they are loaded, saved, and deployed
• Validate git refs before a deployment is queued and again when it starts (#11905)
• Validate environment variable names before they are used in Docker commands and quote docker run -e values (#11917)
• Validate custom internal container names, Compose network names, and static images, and quote them in Docker commands (#11912, #11914, #11958)
• Quote container names, paths, owners, and modes in backup, database start, scheduled task, stop, service, and file storage commands (#11970, #11979, #11983, #11989)
• Validate Compose build paths, file storage paths, and Compose volume paths. Relative file storage paths must stay inside the resource directory, Coolify never deletes host paths outside it or writes through symbolic links there, and API tokens need the deploy permission for mounts outside it (#11911, #11943, #11944, #11993)
• Validate proxy configurations before they are saved (#11923)
• Stop exposing the Traefik dashboard in new proxy configurations and remove the legacy dashboard router from saved ones (restart the proxy to apply)
• Deploy pull requests from other repositories on GitLab, Gitea, and Bitbucket only when public preview deployments are enabled (#11922)
• Hide matching applications in manual webhook responses and throttle repeated distinct signature failures per client address, repository, and branch, without blocking correctly signed deliveries (#11989)
• Require at least 16 characters for new or changed manual webhook secrets
• Reject Stripe webhooks when Stripe is not fully configured (#11915)
• Enforce team ownership and permissions in onboarding, deploy key selection, notification settings, team invitations, and tag deployments (#11913, #11920, #11960, #11966, #11989)
• Use the team that owns a resource instead of the currently selected team for permissions, secret redaction, and selectable servers, destinations, S3 storages, private keys, Git sources, cloud provider tokens, tags, and shared variables, so switching teams in another tab cannot mix teams
• Accept and use only private keys of the same team when adding a server, on GitHub App and GitLab source settings, and for GitHub App tokens, git commands, SSH connections, and backup downloads
• Keep existing SSH private keys out of the browser during onboarding and require update permission on a key to select it
• Hide HTTP basic auth passwords, log drain keys, and the Sentinel token from members without update permission (#11961)
• Hide Docker Compose content, file mount content, environment variable values hardcoded in the Compose file, server shared variable values, and proxy configuration files from members without update permission
• Keep S3 storage keys and database passwords hidden from members after a failed save or a page refresh
• Show container logs and scheduled task commands and output only to users who can update the resource, and require the read:sensitive permission for the log endpoints and scheduled task output in the API
• Return the saved proxy configuration and validation logs of servers in API responses only with the read:sensitive permission
• Keep the reference instead of the value when an environment variable references a locked shared variable
• Show the team Danger Zone only to the team owner
• Prevent root team admins from deleting the root user, root team owners, or their own account in the team admin view
• Check permissions before import file checks on the database import form and before Vultr status refreshes
• Lock the domain and DNS validation state on the Domains pages against changes from the browser
• Require the deploy permission for instant_deploy in the API and accept only known API token permissions (#11969, #11981)
• Enforce the server limit on every server creation path, including the API, onboarding, and cloud providers (#11968)
• Send Git source API requests through the outbound URL guard while still allowing self-hosted Git sources on private networks, and block NAT64 addresses (#11964, #11967)
• Keep secrets out of deployment logs when a command fails, including multiline and literal values (#11974)
• Encrypt remote commands stored for queued tasks, remove them when the task ends, and keep the command line out of error logs, timeout errors, backup logs, and failure notifications
• Require an instance admin for impersonation and the team admin view (#11989)
• Rate limit logins per normalized email address (#11989)
• Update league/commonmark to 2.10.3, which fixes GHSA-8rr7-cvq3-gmfh
• Remove an unused application config download action

Fixed

• Custom container names (#11701)
  • A stored custom name was applied on deploy even when consistent naming was off, while the UI hid the field. Those applications are migrated to consistent naming so their names do not change.
  • Custom names are only used in consistent naming mode. In the API, custom_internal_name turns consistent naming on, and sending it with is_consistent_container_name_enabled: false returns 422.
  • Docker Compose applications ignored the custom name and now use it: web-shop-api instead of web-<uuid>.
  • A name that another application on the same server already uses is no longer saved.
• Deployments
  • Concurrent deployment requests respect the server queue limit, no longer queue duplicates of the same commit, and can no longer start the same queued deployment twice. (#11987)
  • A deployment that cannot be started, for example because of an invalid registry image name, is marked as failed instead of staying in progress and blocking later deployments.
  • An error after the new container passed its health check, for example in a notification, no longer removes the new container or marks the finished deployment as failed.
  • Cancelling a deployment stops the helper container on the build server and on the deployment server, and no longer runs kill -9 on the server with a process ID from the Coolify container.
  • Deployments connect the proxy to the destination network before the containers start.
  • Deleting a server marks its queued deployments as failed instead of leaving them queued.
  • Deploying, closing, or deleting a preview no longer removes the containers of other pull requests whose number starts with the same digits, such as PR 1 and PR 12.
  • Loading pull requests and pull request status updates are only used for applications with a GitHub App source.
• Applications on multiple servers
  • Stop reaches every server even when one of them is unreachable, file mounts are written on every server, and additional servers deploy the same commit, rollback, and image tag as the primary server.
  • Queued deployments on additional servers start when the running deployment finishes or is cancelled.
  • One deployment notification is sent after all servers finish.
  • Deployments without a Docker image name fail with a clear error when started from a webhook or the API.
• Servers
  • A server is marked unreachable only after two consecutive failed connection checks instead of one, and a single failed check no longer marks all resources on the server as exited.
  • Deployments recheck a server that is marked unreachable before failing with "Server is not functional".
  • Queue workers keep using SSH multiplexing after a server connection check.
  • Remote commands that failed on the server are no longer run a second time because their output contained words such as "connection refused". A failed S3 backup upload shows the real error.
  • Containers are matched to their resource by UUID, so containers of another Coolify instance that manages the same server are no longer mixed up with resources that have the same ID.
  • Leftover helper containers are cleaned up on every server instead of one server per run.
  • A manual Docker cleanup that starts while another cleanup runs waits instead of being dropped, and a failed cleanup marks only its own execution as failed.
  • Stopped Hetzner, DigitalOcean, and Vultr servers have the Power On button again.
• Servers with a non-root SSH user
  • Starting and restarting the proxy and loading and saving its configuration work when the user cannot enter the proxy directory.
  • Database starts and backups, application deployments, service starts, the log drain, and volume clones work when the user cannot write to /data/coolify.
  • Pipes inside quoted strings, such as Docker --format templates, are no longer rewritten with sudo.
• Sentinel
  • Sentinel is started with --restart unless-stopped, so Docker restarts it after a crash or reboot.
  • A Sentinel that runs but stopped pushing, or is unhealthy, is restarted, and Sentinel is no longer restarted in a loop while it starts.
  • Two Sentinel starts for the same server no longer collide, and Sentinel checks are skipped on unreachable servers. (#12100)
  • Changing the instance URL updates the Sentinel URL of remote servers that use the generated URL.
  • Container health changes show in the UI after the next push instead of up to five minutes later, and the Sentinel page shows the last push error while Sentinel is out of sync.
• Scheduled jobs and backups
  • Scheduled backups whose queued job was lost are queued again after 60 minutes. Lost scheduled tasks and Docker cleanups are recorded as failed, and the team is notified.
  • One schedule that fails no longer stops the other due schedules, and schedules with a fixed time run once when daylight saving time repeats an hour.
  • Scheduled backups use the current server state instead of a state cached by the queue worker.
  • Backups and scheduled tasks that exceed their timeout fail with the timeout error instead of staying open.
  • Two backups of the same database that start in the same second no longer write the same file, and a backup is skipped while the database starts, restarts, or imports.
  • "All databases" backups of PostgreSQL, MySQL, and MariaDB fail when the dump command fails instead of saving an incomplete archive.
  • In a backup of several databases, every database gets its own result and finish time.
  • Failed volume backup recovery no longer piles up retry jobs or blocks new backups. Executions that need action show "Needs attention" with the reason and a retry button.
  • Settings → Backup loads when the Coolify database has no backup schedule and always uses the instance database.
  • Instance cleanup jobs are no longer blocked for up to 24 hours after a worker was stopped mid-run.
  • php artisan scheduled:diagnostics no longer changes scheduler state.
• Databases
  • "Regenerate SSL Certificates" writes server.crt and server.key for PostgreSQL, MySQL, MariaDB, Redis, KeyDB, and Dragonfly instead of server.pem, so these databases start again, and the CA file on the server matches the CA that signed the certificate.
  • New and regenerated database SSL certificates use a P-256 key, so Electron-based clients such as MongoDB Compass can connect.
  • The MongoDB health check pings the database instead of always passing. (#11730)
  • ClickHouse databases with a file mount keep their data volume. Affected databases keep their current data and ask to adopt it before the next start.
  • Databases and services show their new status right after a start.
• Database restores
  • Single-database MySQL and MariaDB restores decompress .gz archives instead of piping them into the client, and dump-all MySQL restores emit valid shell environment variables. (#11699)
  • Database restores detect the backup format before changing anything. "All databases" imports no longer drop everything when the file cannot be restored, PostgreSQL restores run in one transaction, and replace restores of SQL backups only swap in the new database on success.
  • Interrupted or stale database imports are stopped and cleaned up and no longer block later imports, and a second start, restart, or import while one is running is rejected (409 in the API). Long imports are no longer cut off by the 10-minute task timeout.
  • Imports use the selected source. A checked server path is no longer replaced by an earlier upload that was never imported.
• Compose and storage
  • Compose volumes declared as external are used as declared instead of being renamed to <uuid>_<name>. Existing resources keep their old volume, the deployment log explains how to switch, and the storage page lists external volumes. Preview deployments keep their own volume.
  • Compose volumes keep their driver, driver_opts, and labels when Coolify renames them (volumes created before the upgrade keep their settings), NFS and CIFS volumes are no longer dropped from a service that has other volumes, and ../ bind sources resolve to the parent directory.
  • Deleting a Docker Compose preview removes only the networks and volumes Coolify created for it, instead of every network and volume in the Compose file.
  • Content files are written before the containers start, for every build pack and on every server of the application, and their content is no longer deleted when Docker created a directory at the file's path.
  • File and directory mounts with a relative path are created inside the resource directory instead of the SSH user's home directory, and cloned volumes keep the driver and options of the source volume.
  • Service switches save without saving pending Compose edits, services with an empty Compose file no longer block proxy starts, and Compose comments are kept. (#11985)
  • Starting a service after the configuration of an existing volume changed no longer skips the next start step.
• API
  • GET /applications/{uuid}/logs respects service_name and returns 404 when no running container matches. (#12066)
  • POST /deploy with pull_request_id builds the pull request instead of the base branch for deploy key and public repository applications.
  • Creating a Docker Compose application no longer generates an unused top-level domain.
  • Pull request IDs above the integer range return a validation error instead of a 500, also in the MCP deploy tool.
  • Database create requests are validated (422 for invalid input), accept numeric resource limits, and read instant_deploy as a boolean.
  • The database list no longer returns backup configurations of another database type with the same ID.
  • GET /servers/{uuid}/domains?uuid=<application uuid> filters by application instead of returning 404.
  • The API reference documents PATCH /security/keys/{uuid} instead of PATCH /security/keys.
• Event toggles on the Email notification settings page work again. (#11512)
• Email notification and log drain settings are restored when enabling them fails, other notification toggles return to their saved state when saving fails, and conflicting email providers can no longer be enabled together. (#10543)
• Resend errors show a clear message, and an email that Resend did not accept is no longer counted as sent.
• A proxy in a restart loop sends at most one "container restarted" notification per hour.
• GitLab OAuth sign-in reads the user from GitLab API v4 instead of the removed v3 endpoint.
• Revoking or expiring a team invitation no longer deletes a user who already joined another team.
• Pages that stay open while you switch teams in another tab no longer fail when realtime events arrive.
• Members get a 403 instead of a 500 on the Cloud Tokens page, and non-admins are redirected from the OAuth settings page.
• Gitea preview deployments use the pull request's head commit instead of HEAD.
• Webhooks with pushes without commits or malformed payload values get a clean response instead of a 500.
• Re-checking DNS replaces a stored result, so application, service, and preview domains no longer keep their first status. (#11951)
• DNS checks compare IPv6 addresses by value, so the same address written differently matches.
• Copying DNS record values from the DNS entries dialog works on instances served over plain HTTP.
• Services on unreachable servers can be removed from Coolify only. Deleting any resource on an unreachable server warns that its Docker resources stay on the server and notifies the team afterwards.
• The service list no longer becomes empty when the template CDN returns an empty or invalid response.
• The Grafana admin user and password fields show for Grafana images with a registry prefix, such as docker.io/grafana/grafana. (#10617)
• The terminal shows an error instead of an endless "connecting…" spinner when a session cannot start.
• The Logs page shows why containers could not be loaded instead of "No containers are running".
• Applications without a configuration snapshot show pending configuration changes again.
• "Generate default" for the custom Nginx configuration of a static site with SPA enabled generates the SPA configuration.
• Saving an environment variable shows validation errors instead of a generic error.
• The "Never" expiry of a new API token is kept instead of falling back to 30 days.
• GitHub sources have the Test connection button again.
• The duplicate check for private keys only looks at the team the key belongs to.
• The 2FA setup URL on the profile page is shown and copied with & instead of &.
• The Help form shows an error when the feedback could not be delivered.
• Quick adding tags with special characters, such as apostrophes, works. (#11971)
• Additional destinations can no longer be added twice.
• Applications with a git:// repository URL no longer crash when showing commit links.
• Running the install script again no longer changes the owner and permissions of resource data under /data/coolify, and it waits for the Docker daemon on OpenRC.
• The daily database cleanup deletes old rows in batches instead of one long DELETE.

Services

New

• 9router: AI coding gateway that routes coding assistant requests to 40+ LLM providers with fallback (#11592)
• Bulwark: JMAP webmail (#11180)
• Docling: converts PDF, DOCX, PPTX, images, and HTML to Markdown and JSON (#9121)
• Engram: persistent memory sync server for AI coding agents over MCP (#10808)
• Hermes Agent: autonomous AI agent with persistent memory, scheduling, and a web dashboard (#10703)
• Honcho: memory and reasoning for personalized AI agents (#11184)
• Lidarr: music collection manager for Usenet and BitTorrent (#11576)
• Linkwarden: collaborative bookmark manager that preserves web pages (#11561)
• Obsidian: the Obsidian desktop app in the browser (#10704)
• OpenWA and OpenWA with PostgreSQL and Redis: self-hosted WhatsApp API gateway with a dashboard (#11448)
• PeerTube: decentralized video platform (#9564)
• Portabase: database backup and monitoring (#11054)
• Snipe-IT: IT asset management (#10544)
• Zero: query-driven sync engine for TypeScript apps backed by Postgres (#10713)

Updated

• Appwrite 2.0.0. New Appwrite services use PostgreSQL instead of MariaDB. (#10810)
• Authentik 2026.5.6, with data stored in ./data instead of ./media. (#8791)
• Autobase 2.11.0 with DBDesk Studio. (#9850, #11749)
• Beszel Agent 0.19.0 with configurable LISTEN and HUB_URL. (#11647)
• Bugsink requires an admin email and adds email, site title, and time zone settings.
• Budibase no longer runs Watchtower.
• EMQX Enterprise 6.2.2. (#10922)
• Garage 2.3.0 with a generated access key, secret key, and default bucket. (#10735)
• Hermes Agent with WebUI uses Hermes Agent v2026.6.5 and Hermes WebUI 0.51.489. (#10702)
• Homarr 1.74.0. (#9821)
• Karakeep 0.33.2 with the Karakeep Chrome image and Meilisearch 1.41.0. (#11245)
• Plausible 3.2.1, which fixes CVE-2026-8467. ClickHouse settings match upstream: a 30-day query log, IPv4-only listening, and lower resource usage. (#10975, #11939)
• Pterodactyl Panel and Pterodactyl with Wings 1.12.3 are available again. (#11173)
• Rallly uses PostgreSQL 18, requires an initial admin email, and adds a registration toggle.
• SigNoz 0.137.1 with ClickHouse 25.12.5. (#11346)
• Terraria Server 1.4.5.0 with a generated server password. (#11322)
• Vikunja and Vikunja with PostgreSQL have health checks and use VIKUNJA_SERVICE_SECRET. (#10331)
• Mattermost is marked as AMD64 only.
• osTicket is hidden from the service list. (#10621)

Fixed

• AFFiNE: the Postgres health check uses the configured user instead of affine.
• Budibase: one-click deployments work with the budibase/database image. (#9828)
• Bugsink: superuser creation works, and the MySQL user and password show in the UI. (#11225)
• Buzz: desktop app origins are allowed by CORS. (#11046, #11741)
• Chatwoot: the Sidekiq health check is lighter. (#10920)
• Chibisafe: uploaded files are served from the correct uploads volume. (#11804)
• CyberChef: uses port 8080. (#11170)
• Deno KV: its options show up again. The template is renamed from denoKV to deno-kv, and the old key still works in the API and for existing services.
• Dozzle with auth: documents the bcrypt password hash and the correct default password. (#11235)
• Fider: BASE_URL no longer includes the port, which caused CSP errors. (#11682)
• OpenClaw: the generated username shows in the UI. (#8629)
• Rallly: login no longer fails with an invalid origin error. (#9536)
• SigNoz: no more broken pipe errors. (#11640)
• TriliumNext: runs on ARM64. The health check uses Node instead of wget.
• Twenty: connects to its backend again. (#11562)
• Vaultwarden: fresh installs with Vaultwarden 1.37 work with the SQLite database URL. (#11471)

Removed

• Unused persistent storage Show Livewire component and view. (#11615)
• Unused Blade and Livewire components and views.
• Legacy Laravel Dusk browser tests, DuskServiceProvider, and the laravel/dusk dependency. Browser tests use the Pest browser plugin.
• Laravel Nightwatch integration: the laravel/nightwatch dependency, the Nightwatch agent service in the Coolify container, and the NIGHTWATCH_ENABLED setting.
• Settings → Scheduled Jobs monitoring page.
• The PROXY_CONNECT_NETWORKS_INTERVAL_SECONDS setting.
• The TrustHosts middleware, which never checked the host.

Refactored

• Container name generation uses one code path for single-container and Compose applications. (#11701)
• Database start command execution is extracted into a shared service and job. (#11474)
• Action buttons share one split-button component, removing duplicated markup and CSS. (#11409)
• Volumes and directory mounts are separated in the storage UI. (#7591)
• Team broadcast events share one trait and always name their team.

Issues

• Fixes #11870
• Fixes #11950
• Fixes #11978
• Fixes #11980
• Fixes #11982
• Fixes #11986
• Fixes #11044
• Fixes #12075
• Fixes #12074
• Fixes #12059
• Fixes #12055
• Fixes #11945
• Fixes #11926
• Fixes #11728
• Fixes #10388
• Fixes #6771
• Fixes #4255
• Fixes: #4956
• Fixes: #8508
• Fixes: TriliumNext/Trilium#6390
• Fixes: #11171
• Fixes: #10786
• Fixes: #9303
• Fixes: #11243
• Fixes: #11051
• Fixes: #4250
• Implements #6188
• Implements #3130
• Implements #10594
• Implements #11833
• Partially implements #2499

New uNmINeD development snapshot is available for download!

Changes:

• Fixed lossy WebP transparent background
• Missing Bedrock LevelDB *.ldb files are ignored instead of throwing an error
• Added LibDeflate for linux-musl (Alpine) builds for speed
• Improved Bedrock to Java block conversion speed
• 2D rendering speed optimizations
• Improved 26.3+ default blockstate resolving speed
• (Isometric) Added 14° pitch angle
• (Isometric) Redesigned block model processing, caching and rendering pipeline
• (Isometric) Huge drop in memory usage
• (Isometric) Improved speed
• (Isometric) Improved CPU utilization
• (Isometric) Fixed crashes when using image adjustments

Notes:

• Isometric image and web export is not yet available
• Documentation and howto’s for isometric mode are coming soon

Setting up isometric mode:

• Isometric mode and the experimental block model rendering needs a Java Edition client JAR file for both Java and Bedrock worlds. Select one in World/App settings menu (“Default Minecraft client JAR to use” setting). If you do not have a Java Edition client installed, you can download a client JAR file from the Minecraft Wiki.
• For Bedrock, select a vanilla resource pack ZIP file in World/App settings. You can download one from GitHub: click on Assets, then download the bedrock-samples-*-full.zip file. Versions does not have to match exactly, using the latest resource pack usually works.

[0.16.25] - 2026-10-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

• JMAP: Creating a MaskedEmail with emailDomain fails with forbidden for every domain when the account has addresses on more than one domain.
• Autodiscover: Requests for a response schema other than Outlook's, such as ActiveSync (mobilesync), are answered with the Outlook settings instead of error 601.
• IMAP:
  • LOGIN and AUTHENTICATE with a wrong, expired or unknown app password or API key are answered with an untagged NO, so clients keep waiting for the command to complete until the connection times out.
  • The failed login that exceeds the maximum number of authentication failures is answered with an untagged NO before the connection is closed.
• DKIM:
  • A rotation moves the active key to retiring even when its successor fails to publish or propagate, so outgoing mail is sent unsigned until a retry publishes the new key. The DNS write failure is also not logged and the task reports success.
  • Keys created while DNS management was manual, or before DKIM was added to the published records, are never rotated after DNS management becomes automatic. Domains already affected start rotating once a DkimManagement task is created for them.
  • After switching DNS management from automatic to manual, a due rotation activates a new key that was never published in DNS, so signatures fail verification, and retiring the old key is retried forever.
• Spam filter:
  • Messages with no text line long enough for a Pyzor digest are checked with the digest of empty input and tagged PYZOR.
  • DNSBL answers with several return codes, such as a Spamhaus ZEN listing in both SBL and PBL, are scored for only the first code returned.
  • DNSBL lookups that return "not listed" are cached for 24 hours regardless of the zone's negative TTL.
  • Removing a duplicate training sample of a message reclassified on the same day clears the blob link of the sample that is kept.
• MTA: Queue quotas with an empty match expression are never enforced, including the global queue quota created on first start.
• RocksDB: The info log (LOG, LOG.old.*) grows without limit because log rotation and retention are left at RocksDB defaults.
• WebUI: A blob store read error at startup, such as an S3 authentication failure, stops the web interface from being downloaded.

Check binary attestation here

📦 Downloads available at

• https://user.bitfocus.io/download

💵 Donate to the project at

• open collective https://opencollective.com/companion

Companion v5.0.7 - Release Notes

🐞 BUG FIXES

• only add imageBuffers layer to simple presets when a feedback declares imageBuffer #4490
• limit preset advanced-feedback style overrides to affectedProperties #4410 #4490
• some surface open race conditions
• update elgato-stream-deck surface module
• layered presets lose all feedbacks when style overrides use plain values (#4477)
• late closeSurface closing a reopened plugin surface
• abort signal not being propagated into module action callback
• move expression stream re-evaluation log to silly level #4489

Full Changelog: v5.0.6...v5.0.7

Security:

• Update to OpenSSL 3.5.9

Security:

• Fixed script injection in event scripts. With JScript, untrusted values passed to event handlers (such as the logon password in OnClientValidatePassword, or error text and UIDs sent by remote servers) could break out of their string. With either script language, a rule's "Run function" name could carry code. This would allow an attacker to run arbitrary code in the hMailServer process. Values are now escaped, and rule function names may only contain letters, digits and underscores.

If you are unable to install this version, disable JScript execution and do not give end-users access to the hMailServer COM API.

Archived hMailServer builds, from 4.1.1 to 5.6.9 build 2607. These versions are no longer supported and are kept for reference only. Use the latest release for new installations.

[0.16.24] - 2026-09-27

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

• DNS: PowerDNS Authoritative provider for automatic DNS record management.

Changed

Fixed

• Troubleshoot tool: TLSA records are looked up for every MX host, including hosts whose zone is not DNSSEC signed.
• Spam filter:
  • OpenPhish and PhishTank entries containing uppercase characters never match, since message URLs are lowercased while HTTP lookup entries keep their original case. HTTP lookups now match keys case-insensitively.
  • URL shortener links are followed using the lowercased URL, so case-sensitive short links resolve to the wrong destination or not at all.
  • Incremental training never advances its position past the first run, so every retained sample added since then is trained again, and counted again in the reservoir, on each run until it expires.
  • Updating the rules only adds new objects, so upstream changes to existing rules, DNSBL servers, HTTP lookups, lookup keys and file extensions never reach an existing installation.
  • Updating the rules reports success when objects fail to import, or when a configuration error stops the updated settings from being activated.
• JMAP:
  • A PushSubscription created within the verification rate limit window of another one on the same account never receives its PushVerification, since the blocked verification is dropped instead of being sent once the window expires.
  • A push notification retried after a failed delivery can report an older state than a change queued during the failed attempt, since the older state changes are merged last and overwrite the newer ones.
  • Changes made while a push request is in flight are not delivered until the next change reaches the same subscription, since a successful delivery cancels the pending retry.
  • The VAPID aud claim is derived from a hand-written parse of the push URL, so a crafted push URL can make the server sign a token for a push service other than the one the request is sent to.
  • Email/import rejects a blobId that refers to a Blob/upload creation id in the same request ("#u0") with Invalid blob id..
  • Email/set with a full mailboxIds object identical to the current mailboxes, together with a keyword change, stores the message with IMAP UID 0, so IMAP clients stop seeing it.
• MTA:
  • A node without the outboundMta role stops replying to DATA and to JMAP submissions once about 1024 messages have been queued on it.
  • MX records are resolved through the DNSSEC-validating resolver even when DANE is disabled.
  • A DATA stage Sieve script does not see headers added by milters or MTA hooks, and discards every milter and MTA hook change when it edits the message.
• MySQL: Range deletions and search index removals start with a single unbounded DELETE and switch to chunks only after a timeout.
• IMAP: COPY and MOVE fail with NO [CONTACTADMIN] when another session changes the same message at the same time.
• Autodiscover: Implicit TLS ports (993, 995, 465) are advertised with <Encryption>TLS</Encryption>, which Outlook reads as STARTTLS.
• HTTP: Idle keep-alive connections are never closed.

Check binary attestation here