Development Build
Below are development builds for testing purposes.
Latest development build: 2.7.1.21 (May 6th 2026)
Latest stable release build: 2.7.1
https://github.com/clsid2/mpc-hc/releases/tag/2.7.1
Below are development builds for testing purposes.
Latest development build: 2.7.1.21 (May 6th 2026)
Latest stable release build: 2.7.1
https://github.com/clsid2/mpc-hc/releases/tag/2.7.1
NEXT_PUBLIC_BASE_PATH environment variableuseTranslations for "selected emails" and "cancel" on email list batch operations
The Asterisk Development Team would like to announce
the release of Certified asterisk-18.9-cert18.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/certified-18.9-cert18
and
https://downloads.asterisk.org/pub/telephony/certified-asterisk
Repository: https://github.com/asterisk/asterisk
Tag: certified-18.9-cert18
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
Author: Naveen Albert
Date: 2022-10-17
Some SIP devices use an empty extension for PLAR functionality.
Rather than rejecting these empty extensions, we now use the s
extension for such calls to mirror the existing PLAR functionality
in Asterisk (e.g. chan_dahdi).
ASTERISK-30265 #close
<style> tag when applying padding

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!
