3.1.1
CSMWrap Version 3.1.1
Changelog since CSMWrap 3.1.0
Miscellaneous bug fixes, mostly surrounding the SeaBIOS storage driver code.
Full Changelog: 3.1.0...3.1.1
Miscellaneous bug fixes, mostly surrounding the SeaBIOS storage driver code.
Full Changelog: 3.1.0...3.1.1
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.
AccountSettings object return invalidProperties.mail-parser panic with certain messages containing corrupted attachments.RCPT on checks.AddressBook/query fetches wrong resources.%EMAILADDRESS% when no email address is provided.
Hi,
The OpenWrt community is proud to announce the third service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
New devices supported in 25.12.3:
Device fixes:
erp_domain and fils_cache_id values generated by the ucode-based config script (#21768)bridge_isolate and network_vlan fields to the ucode schema (#22620)iface and other fields to the ucode station/vlan schema (#22165)set_fixed_freq-u option (skip default configuration) which was broken with apk-f (custom backup) when the path contains spacesDISKSEQ instead of MAJOR/MINOR for stable disk identification (MAJOR/MINOR are not sequential)devpath option for selecting cellular modems by USB device pathkmod-vsock and kmod-vsock-virtio for VM guests (vsock communication)Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4, and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
Meraki MX60: Direct sysupgrade to 25.12.3 is not possible without manual preparation β meraki_loadaddr must be changed before upgrading, as the default value is insufficient to boot OpenWrt 25.12+. See the device wiki page for instructions.
eth1 to wan β check and update your network configuration after upgrading.cake_mq): throughput may be unexpectedly low on some configurations after the scheduler fixes in this release. #22344Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.3
In particular, make sure to read the known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.3#known_issues
For a detailed list of all changes, refer to
https://openwrt.org/releases/25.12/changelog-25.12.3
To download the 25.12.3 images, navigate to:
https://downloads.openwrt.org/releases/25.12.3/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.3
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
Have fun!
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
other announcement channels (such as RSS feeds) might be added in
the future, they will be listed at https://openwrt.org/contact
$PIR table is now synthesized from ACPI _PRT/_PRS and handed to SeaBIOS so legacy OSes can get non-ACPI PCI IRQ routing.Set Power State (off/reboot) now trampolines through the helper core into UEFI's ResetSystem runtime service. Previously these calls were no-ops.csmwrap.ini options (system_thread, cpu_allowlist, cpu_blocklist) let you pin the BIOS proxy helper core to a specific APIC ID and hide arbitrary APs.Full Changelog: 3.0.1...3.1.0
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
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.
userinfo endpoint when JWT token does not contain an email claim.verifyAfterWrite option to verify that objects have persisted after writing.credentialId when there are password changes.
Note
If someone is asking you to pay money for access to UpSnap binaries, source code, or licenses, you are being scammed.
The official and only trusted source for UpSnap is this repository (and its linked releases).
Do not pay third parties for something that is provided here for free.
Docker images have been built and pushed:
Docker Hub:
alexta69/metube:latestalexta69/metube:2026.04.26GitHub Container Registry:
ghcr.io/alexta69/metube:latestghcr.io/alexta69/metube:2026.04.26
This version includes multiple breaking changes. If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
system('node_hostname') and system('node_role') expression variables to retrieve the local node hostname and cluster role respectively.receivedAt headers after importing (#2939).receivedAt headers.BINARY fetch responses (#2940).CAA record updates.
Windows Installer
Windows No Installer (zip)
macOS - Universal
Linux - deb, AppImage or rpm
Windows intel x32 releases are marked -ia32-
ChangeLog:
OBS-Studio-32.1.2-Sources.tar.gz: c6532380c68a75327fe8b551461adeca8f184dcbe4015096251a6de76362a554
OBS-Studio-32.1.2-Ubuntu-24.04-x86_64-dbsym.ddeb: 3cf56a96de5d0b45f641e8415d3dacc1e47dfc897ba5bcd118b3af05a9ea76da
OBS-Studio-32.1.2-Ubuntu-24.04-x86_64.deb: a3bb1b0176604dad9e22710e057f0fdd76e8afb600e0e1914c30464ae49908e8
OBS-Studio-32.1.2-Windows-arm64-PDBs.zip: 609c4cd849f8d225b021a5f50a080c31af8beb1b5275f2b0088318ab80b0ed78
OBS-Studio-32.1.2-Windows-arm64.zip: 5e1e400e1b49d2019c97c928873229336c8e0b56df488663532376485746328e
OBS-Studio-32.1.2-Windows-x64-Installer.exe: 94d180c1fc481ccc307b95513f795d088d63ac4f61ad3253c2ac0d94d0844110
OBS-Studio-32.1.2-Windows-x64-PDBs.zip: 8105fed359f3437819264b0ebb1c50db6d3bb30de1a65d4a3049e3c14f88deb8
OBS-Studio-32.1.2-Windows-x64.zip: 8d97e4563bd8d22d03e63042aa7dccede1d555c9bd35ce8a9e5019b0d0201bf6
OBS-Studio-32.1.2-macOS-Apple-dSYMs.tar.xz: eea32d7c022237e163a02f8f2fdc26c8b1a0d4a4fc3fb49aaf14df7b59b3d668
OBS-Studio-32.1.2-macOS-Apple.dmg: 2aeb3aaa99544fefd557f10ac6550e73df71540dd57528b2a1e6f39a55ebacfb
OBS-Studio-32.1.2-macOS-Intel-dSYMs.tar.xz: 6a06ed32e0626cafcb7d4f53074b80e63329c1c99309c7f5898d469ed0ef307c
OBS-Studio-32.1.2-macOS-Intel.dmg: f7febee4c52e97930ffa9d8bcae79ee4c60c411827688cfbe36bc53edc51616e
Docker images have been built and pushed:
Docker Hub:
alexta69/metube:latestalexta69/metube:2026.04.21GitHub Container Registry:
ghcr.io/alexta69/metube:latestghcr.io/alexta69/metube:2026.04.21
This version includes multiple breaking changes. If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
zxcvbn algorithmMX, TXT, CNAME, SRV, CAA and TLSA records (#463 #1017 #1419 #2438 #1370 #1406 #1371)TLSA records when ACME certificates change (#1664)SIG(0) support (#856)smtp, imap and memory directory backends.aws-lc for cryptographic operations instead of ring.rustls-platform-verifier for TLS certificate verification instead of webpki (#247).inMailboxOtherThan query logic.hasAttachment search field (#2778)8000 bytesRIGHTS capability (#2762)ACL SET permission override.304 NOT_MODIFIED on If-None-MatchPUT requests if they are equal to the existing ones.id sorteable.204 CORS preflight responses
Windows Installer
Windows No Installer (zip)
macOS - Universal
Linux - deb, AppImage or rpm
Windows intel x32 releases are marked -ia32-
ChangeLog:
Docker images have been built and pushed:
Docker Hub:
alexta69/metube:latestalexta69/metube:2026.04.16GitHub Container Registry:
ghcr.io/alexta69/metube:latestghcr.io/alexta69/metube:2026.04.16
Docker images have been built and pushed:
Docker Hub:
alexta69/metube:latestalexta69/metube:2026.04.12GitHub Container Registry:
ghcr.io/alexta69/metube:latestghcr.io/alexta69/metube:2026.04.12