Apple reports second quarter results


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.
STALWART_HTTPS_PORT with STALWART_PUBLIC_URL.app_ instead of app to avoid issues with some clients that do not support spaces in passwords.INFO.
@directus/schema-builder dependency (#27166 by @ComfortablyCoding)VERSION_SAVE activity/revisions not respecting collection tracking settings (#27096 by @yogeshwaran-c)/ in name (#27114 by @costajohnt)directus_access junction collection (#27152 by @yogeshwaran-c)useShortcut attempting to access document before available (#27155 by @ComfortablyCoding)@directus/app@15.10.0@directus/api@35.2.0@directus/composables@11.4.1create-directus-extension@11.0.36@directus/env@5.8.0@directus/extensions@3.0.25@directus/extensions-registry@3.0.26@directus/extensions-sdk@17.1.4@directus/memory@3.1.8@directus/pressure@3.0.22@directus/schema-builder@0.0.20@directus/storage-driver-azure@12.0.22@directus/storage-driver-cloudinary@12.0.22@directus/storage-driver-gcs@12.0.22@directus/storage-driver-s3@12.1.8@directus/storage-driver-supabase@3.0.22@directus/themes@1.3.3@directus/types@15.0.3@directus/utils@13.4.1@directus/validation@2.0.23@directus/visual-editing@2.0.1@directus/sdk@21.3.0@directus/sandbox@0.0.0
General
HLS
WebRTC
RPI Camera
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
HLS
General
API
RTSP
HLS
Dependencies
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
General
RTSP
RTMP
WebRTC
RPI Camera
Dependencies
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
WebRTC
API
General
API
RTSP
HLS
WebRTC
Dependencies
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
General
HLS
Dependencies
Binaries are compiled from source code by the Release workflow without human intervention.
You can verify that binaries have been produced by the workflow by using GitHub Attestations:
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
General
API
RTMP
HLS
WebRTC
SRT
RPI Camera
Dependencies
Binaries are compiled from source code by the Release workflow without human intervention.
You can verify that binaries have been produced by the workflow by using GitHub Attestations:
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
General
RTSP
RPI Camera
Dependencies
Binaries are compiled from source code by the Release workflow without human intervention.
You can verify that binaries have been produced by the workflow by using GitHub Attestations:
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
General
API
WebRTC
General
API
RTSP
HLS
WebRTC
RPI Camera
Dependencies
Binaries are compiled from source through the Release workflow without human intervention, preventing any external interference.
You can verify that binaries have been produced by the workflow by using GitHub Attestations:
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
General
RTSP
SRT
Dependencies
Binaries are compiled from source through the Release workflow without human intervention, preventing any external interference.
You can verify that binaries have been produced by the workflow by using GitHub Attestations:
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
General
API
RTSP
RTMP
Dependencies
Binaries are compiled from source through the Release workflow without human intervention, preventing any external interference.
You can verify that binaries have been produced by the workflow by using GitHub Attestations:
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
This is a security release to improve attachment related permission checks, and URL validation for webhooks.
Upgrade is advised if you allow untrusted users to delete attachments, or if untrusted users have permission to create webhooks on instances which make use of the ALLOWED_SSR_HOSTS BookStack env file option.
Thanks to 404_pkj (GitHub) and naruhodoowl (GitHub) for responsibly reporting these issues.
The Stable channel has been updated to 148.0.7778.96/.97 for Windows and Mac as part of our early stable release to a small percentage of users. A full list of changes in this build is available in the log.
You can find more details about early Stable releases here.
Interested in switching release channels? ย Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.
Srinivas Sista
Google Chrome
Truckers, start your engines and get ready to roll through The Prairie State! From the towering skyline of Chicago to the highways that carry freight across the Midwest and beyond, weโre excited to announce that the..
Weโre just as excited as you are! To keep the wheels turning, weโve released the official Illinois DLC trailer on our YouTube channel. Put together by our talented video team, it offers a glimpse into the diverse landscapes, iconic landmarks, industries and cities waiting for you on the road. Be sure to check it out, and if you enjoy it, drop a like and let us know what you think!

VIENNA, Austria โ April 29, 2026 โ Leading open-source server solutions provider Proxmox Server Solutions GmbH (henceforth "Proxmox") today announced the release of Proxmox Backup Server 4.2. This update is based on Debian 13.4 โTrixieโ, bringing updated packages, improved hardware support, and enhanced security. Proxmox Backup Server 4.2 ships with Linux kernel 7.0 as the new stable default and includes ZFS 2.4 for reliable, enterprise-grade storage. The new release also delivers major improvements in backup data organization, sync security, sync performance, S3-backed storage, and the underlyingย software stack.
Support for moving groups and namespaces
Backup groups and namespaces can now be moved to different locations within the same datastore. This gives administrators more flexibility when reorganizing existing backups, while per-group locking helps ensure data consistency throughout the process.
Server-side en/decryption support for sync jobs
Push sync jobs can now be configured to encrypt snapshots on the fly before sending them to remote datastores. This is particularly useful when synchronizing backup data to less trusted remote Proxmox Backup Server instances. In addition, pull sync jobs can be configured to decrypt snapshots that were encrypted on remote datastores. To make key management easy, tape and sync encryption keys can now all be managed from the same centralized panel.
Concurrent group pull/push support for sync jobs
Sync jobs can now process multiple groups in parallel through the new worker-threads property. This significantly improves throughput on high-latency networks and helps overcome HTTP/2 connection limitations. Logging has also been improved, with contextual prefixes for log messages and better visibility for push sync jobs.
S3-compatible object stores as backup storage backend
S3-compatible object stores are now officially supported as a backup storage backend. S3-backed datastores can now also track request counts and traffic statistics for deeper operational insight and monitoring. This is especially useful for identifying unexpected traffic volume early. The request counters are visualized in the datastore summary.
Proxmox Backup Server 4.2 is immediately available for download. Users can obtain a complete installation image via ISO download, which contains the full feature set of the solution and can be installed quickly on bare-metal systems using an intuitive installation wizard.
Seamless distribution upgrades from older versions of Proxmox Backup Server are possible using the standard APT package management system. Furthermore, it is also possible to install Proxmox Backup Server on top of an existing Debian installation. As Free/Libre and Open Source Software (FLOSS), the entire solution is published under the GNU AGPLv3.
For enterprise users, Proxmox Server Solutions GmbH offers professional support through subscription plans. Pricing for these subscriptions starts at EUR 560 per server per year, including unlimited backup storage and unlimited backup clients. A subscription provides access to the stable Enterprise Repository with timely updates via the web interface, as well as certified technical support. It is recommended for production use.
Resources:
###
About Proxmox Backup Server
Proxmox Backup Server is an enterprise backup solution for backing up and restoring virtual machines, containers, and physical hosts. The open-source client-server software supports incremental backups, deduplication, Zstandard compression, and authenticated encryption. Designed for efficiency and ease of use, Proxmox Backup Server enables users to back up data in a space-efficient manner and restore virtual machines, archives, or single objects quickly. With its web-based user interface, the solution helps reduce administrative effort through simplified management. Proxmox Backup Server is licensed under the GNU AGPLv3. Enterprise support subscriptions are available from Proxmox.
About Proxmox Server Solutions
Proxmox provides powerful and user-friendly open-source server software. Enterprises of all sizes and industries use the Proxmox solutions to deploy efficient and simplified IT infrastructures, minimize total cost of ownership, and avoid vendor lock-in. Proxmox also offers commercial support, training services, and an extensive partner ecosystem to ensure business continuity for its customers. Proxmox Server Solutions GmbH was established in 2005 and is headquartered in Vienna, Austria. To learn more visit https://www.proxmox.com. Further information is available on LinkedIn and on YouTube.
Contact: Michael Hiess, Proxmox Server Solutions GmbH, marketing@proxmox.com
![]()
The Extended Stable channel has been updated to 146.0.7680.216ย for Windows and Mac which will roll out over the coming days/weeks.