The Stable channel has been updated to 144.0.7559.109/.110 for Windows/Mac and 144.0.7559.109 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[$3000][474435504] High CVE-2026-1504: Inappropriate implementation in Background Fetch API. Reported by Luan Herrera (@lbherrera_) on 2026-01-09
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
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.
26.1 Snapshot 5 (known as 26.1-snapshot-5 in the launcher) is the fifth snapshot for Java Edition 26.1, released on January 27, 2026.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-snapshot-5
Firefox now allows you to customize your keyboard shortcuts to replace hard-to-type or hard-to-remember hotkeys, eliminate conflicts with other software, and create your preferred set. Access this experimental new feature by typing about:keyboard in the address bar and please share your feedback with us on Mozilla Connect!
Fixed
Resolved various issues with missing or impaired browser functionality when using XDG Base Directories on Linux. (Bug 2011300)
Fixed an issue causing excess passkey prompts to appear when logging into some sites. (Bug 2010919)
Fixed an issue that could lead to sites being incorrectly flagged as malicious by SafeBrowsing. (Bug 2010956)
Fixed an issue where player could get stuck on "Opening" when the graph worker thread malfunctioned. This happened on a few Windows 11 systems when opening files from Windows Search. We were unable to reproduce it, so root cause is unknown, likely an obscure Windows bug.
[p]Molotov/incendiary grenades that bounce off an enemy player have a one-time fuse extension added to prevent them from air-bursting when their has-never-hit-the-world timer elapses.[/p][/*]
[p][/p][p]\[ SOUND ][/p]
[p]Fixed a performance issue when running CS2 without a sound device.[/p][/*]
[p]Various knife sound adjustments.[/p][/*]
[p][/p][p]\[ MISC ][/p]
[p]Fixed broken cl_ent_bbox visualization for some classes of rigid dynamic entities.[/p][/*]
[p]Various stability improvements.[/p][/*]
[p][/p][p]\[ MAPS ][/p][p]Nuke[/p]
[p]Adjusted hanging hard hat model render bounds to prevent shadow popping when model exited the view frustum.[/p][/*]
[p]Warden[/p]
[p]Updated to the latest version from the Community Workshop (Update Notes)[/p][/*]
[p]Sanctum[/p]
[p]Updated to the latest version from the Community Workshop (Update Notes)[/p][/*]
If you like Part-DB, consider donating to support the development. Press the sponsor button on the main github page, for more info.
Important
If you are using Part-DB it would be helpful if you fill out this short survey on your usage of Part-DB (Google Forms): https://forms.gle/Q15twx3YYq3qCNfe8
Improvements
When using the "upload files" button automatically determine a fitting attachment type based on extension
Support SPN columns for all suppliers as columns in BOM imports, not only LCSC (PR#1208, thanks @MayNiklas)
Bug fixes
Disable the ID search by default, like intended in PR #1184
Use correct language for sidebar trees, even if no user is logged in
Prevent ordering of extra column in log tables, as this errors on Postgres and has no real use
Show an error popup instead of a 500 page when info provider retrieval fails
Added clear button for part select input in BOMs (#1156)
#1231 fix http desync if the urlform global-option was changed to get
this initial fix only applies when reverse-proxied, in which case copyparty will now always connection:close (don't reuse tcp/uds connections), as giving each client a fresh socket helps avoid all such issues e1eff21b4fddbc
the expected performance impact from this change is near-zero for real use, even if benchmarks show a 40% reduction in requests/sec in the absolute-worst-case (burst of cheap requests)
a future version will also fix this issue for non-proxied clients
The category name in the chan_websocket.conf.sample file was
incorrect. It should be "global" instead of "general".
cli.c: Allow 'channel request hangup' to accept patterns.
The 'channel request hangup' CLI command now accepts
multiple channel names, POSIX Extended Regular Expressions, glob-like
patterns, or a combination of all of them. See the CLI command 'core
show help channel request hangup' for full details.
res_sorcery_memory_cache: Reduce cache lock time for sorcery memory cache populate command
The AMI command sorcery memory cache populate will now
return an error if there is an internal error performing the populate.
The CLI command will display an error in this case as well.
res_geolocation: Fix multiple issues with XML generation.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-level
PIDF-LO device, person or tuple elements.
device_id which sets the content of the <deviceID> element.
Both parameters can include channel variables.
res_pjsip_messaging: Add support for following 3xx redirects
A new pjsip endpoint option follow_redirect_methods was added.
This option is a comma-delimited, case-insensitive list of SIP methods
for which SIP 3XX redirect responses are followed. An alembic upgrade
script has been added for adding this new option to the Asterisk
database.
taskprocessors: Improve logging and add new cli options
New CLI command has been added -
core show taskprocessor name
ccss: Add option to ccss.conf to globally disable it.
A new "enabled" parameter has been added to ccss.conf. It defaults
to "yes" to preserve backwards compatibility but CCSS is rarely used so
setting "enabled = no" in the "general" section can save some unneeded channel
locking operations and log message spam. Disabling ccss will also prevent
the func_callcompletion and chan_dahdi modules from loading.
Makefile: Add module-list-* targets.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
app_mixmonitor: Add 's' (skip) option to delay recording.
This change introduces a new 's()' (skip) option to the MixMonitor
application. Example:
MixMonitor(${UNIQUEID}.wav,s(3))
This skips recording for the first 3 seconds before writing audio to the file.
Existing MixMonitor behavior remains unchanged when the 's' option is not used.
app_queue.c: Only announce to head caller if announce_to_first_user
When announce_to_first_user is false, no announcements are played to the head caller
Upgrade Notes:
res_geolocation: Fix multiple issues with XML generation.
Geolocation: In order to correct bugs in both code and
documentation, the following changes to the parameters for GML geolocation
locations are now in effect:
The documented but unimplemented crs (coordinate reference system) element
has been added to the location_info parameter that indicates whether the 2d
or 3d reference system is to be used. If the crs isn't valid for the shape
specified, an error will be generated. The default depends on the shape
specified.
The Circle, Ellipse and ArcBand shapes MUST use a 2d crs. If crs isn't
specified, it will default to 2d for these shapes.
The Sphere, Ellipsoid and Prism shapes MUST use a 3d crs. If crs isn't
specified, it will default to 3d for these shapes.
The Point and Polygon shapes may use either crs. The default crs is 2d
however so if 3d positions are used, the crs must be explicitly set to 3d.
The geoloc show gml_shape_defs CLI command has been updated to show which
coordinate reference systems are valid for each shape.
The pos3d element has been removed in favor of allowing the pos element
to include altitude if the crs is 3d. The number of values in the pos
element MUST be 2 if the crs is 2d and 3 if the crs is 3d. An error
will be generated for any other combination.
The angle unit-of-measure for shapes that use angles should now be included
in the respective parameter. The default is degrees. There were some
inconsistent references to orientation_uom in some documentation but that
parameter never worked and is now removed. See examples below.
Examples...
The threadpool_* options in pjsip.conf have now
been deprecated though they continue to be read and used.
They have been replaced with taskpool options that give greater
control over the underlying taskpool used for PJSIP. An alembic
upgrade script has been added to add these options to realtime
as well.
app_directed_pickup.c: Change some log messages from NOTICE to VERBOSE.
In an effort to reduce log spam, two normal progress
"pickup attempted" log messages from app_directed_pickup have been changed
from NOTICE to VERBOSE(3). This puts them on par with other normal
dialplan progress messages.
Developer Notes:
ccss: Add option to ccss.conf to globally disable it.
A new API ast_is_cc_enabled() has been added. It should be
used to ensure that CCSS is enabled before making any other ast_cc_* calls.
chan_websocket: Add ability to place a MARK in the media stream.
Apps can now send a MARK_MEDIA command with an optional correlation_id parameter to chan_websocket which will be placed in the
media frame queue. When that frame is dequeued after all intervening media
has been played to the core, chan_websocket will send a MEDIA_MARK_PROCESSED event to the app with the same correlation_id
(if any).
chan_websocket: Add capability for JSON control messages and events.
The chan_websocket plain-text control and event messages are now
deprecated (but remain the default) in favor of JSON formatted messages.
See https://docs.asterisk.org/Configuration/Channel-Drivers/WebSocket for
more information.
A "transport_data" parameter has been added to the
The category name in the chan_websocket.conf.sample file was
incorrect. It should be "global" instead of "general".
cli.c: Allow 'channel request hangup' to accept patterns.
The 'channel request hangup' CLI command now accepts
multiple channel names, POSIX Extended Regular Expressions, glob-like
patterns, or a combination of all of them. See the CLI command 'core
show help channel request hangup' for full details.
res_sorcery_memory_cache: Reduce cache lock time for sorcery memory cache populate command
The AMI command sorcery memory cache populate will now
return an error if there is an internal error performing the populate.
The CLI command will display an error in this case as well.
res_geolocation: Fix multiple issues with XML generation.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-level
PIDF-LO device, person or tuple elements.
device_id which sets the content of the <deviceID> element.
Both parameters can include channel variables.
res_pjsip_messaging: Add support for following 3xx redirects
A new pjsip endpoint option follow_redirect_methods was added.
This option is a comma-delimited, case-insensitive list of SIP methods
for which SIP 3XX redirect responses are followed. An alembic upgrade
script has been added for adding this new option to the Asterisk
database.
taskprocessors: Improve logging and add new cli options
New CLI command has been added -
core show taskprocessor name
ccss: Add option to ccss.conf to globally disable it.
A new "enabled" parameter has been added to ccss.conf. It defaults
to "yes" to preserve backwards compatibility but CCSS is rarely used so
setting "enabled = no" in the "general" section can save some unneeded channel
locking operations and log message spam. Disabling ccss will also prevent
the func_callcompletion and chan_dahdi modules from loading.
Makefile: Add module-list-* targets.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
app_mixmonitor: Add 's' (skip) option to delay recording.
This change introduces a new 's()' (skip) option to the MixMonitor
application. Example:
MixMonitor(${UNIQUEID}.wav,s(3))
This skips recording for the first 3 seconds before writing audio to the file.
Existing MixMonitor behavior remains unchanged when the 's' option is not used.
app_queue.c: Only announce to head caller if announce_to_first_user
When announce_to_first_user is false, no announcements are played to the head caller
Upgrade Notes:
res_geolocation: Fix multiple issues with XML generation.
Geolocation: In order to correct bugs in both code and
documentation, the following changes to the parameters for GML geolocation
locations are now in effect:
The documented but unimplemented crs (coordinate reference system) element
has been added to the location_info parameter that indicates whether the 2d
or 3d reference system is to be used. If the crs isn't valid for the shape
specified, an error will be generated. The default depends on the shape
specified.
The Circle, Ellipse and ArcBand shapes MUST use a 2d crs. If crs isn't
specified, it will default to 2d for these shapes.
The Sphere, Ellipsoid and Prism shapes MUST use a 3d crs. If crs isn't
specified, it will default to 3d for these shapes.
The Point and Polygon shapes may use either crs. The default crs is 2d
however so if 3d positions are used, the crs must be explicitly set to 3d.
The geoloc show gml_shape_defs CLI command has been updated to show which
coordinate reference systems are valid for each shape.
The pos3d element has been removed in favor of allowing the pos element
to include altitude if the crs is 3d. The number of values in the pos
element MUST be 2 if the crs is 2d and 3 if the crs is 3d. An error
will be generated for any other combination.
The angle unit-of-measure for shapes that use angles should now be included
in the respective parameter. The default is degrees. There were some
inconsistent references to orientation_uom in some documentation but that
parameter never worked and is now removed. See examples below.
Examples...
The threadpool_* options in pjsip.conf have now
been deprecated though they continue to be read and used.
They have been replaced with taskpool options that give greater
control over the underlying taskpool used for PJSIP. An alembic
upgrade script has been added to add these options to realtime
as well.
app_directed_pickup.c: Change some log messages from NOTICE to VERBOSE.
In an effort to reduce log spam, two normal progress
"pickup attempted" log messages from app_directed_pickup have been changed
from NOTICE to VERBOSE(3). This puts them on par with other normal
dialplan progress messages.
Developer Notes:
ccss: Add option to ccss.conf to globally disable it.
A new API ast_is_cc_enabled() has been added. It should be
used to ensure that CCSS is enabled before making any other ast_cc_* calls.
chan_websocket: Add ability to place a MARK in the media stream.
Apps can now send a MARK_MEDIA command with an optional correlation_id parameter to chan_websocket which will be placed in the
media frame queue. When that frame is dequeued after all intervening media
has been played to the core, chan_websocket will send a MEDIA_MARK_PROCESSED event to the app with the same correlation_id
(if any).
chan_websocket: Add capability for JSON control messages and events.
The chan_websocket plain-text control and event messages are now
deprecated (but remain the default) in favor of JSON formatted messages.
See https://docs.asterisk.org/Configuration/Channel-Drivers/WebSocket for
more information.
A "transport_data" parameter has been added to the
The category name in the chan_websocket.conf.sample file was
incorrect. It should be "global" instead of "general".
cli.c: Allow 'channel request hangup' to accept patterns.
The 'channel request hangup' CLI command now accepts
multiple channel names, POSIX Extended Regular Expressions, glob-like
patterns, or a combination of all of them. See the CLI command 'core
show help channel request hangup' for full details.
res_sorcery_memory_cache: Reduce cache lock time for sorcery memory cache populate command
The AMI command sorcery memory cache populate will now
return an error if there is an internal error performing the populate.
The CLI command will display an error in this case as well.
res_geolocation: Fix multiple issues with XML generation.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-level
PIDF-LO device, person or tuple elements.
device_id which sets the content of the <deviceID> element.
Both parameters can include channel variables.
res_pjsip_messaging: Add support for following 3xx redirects
A new pjsip endpoint option follow_redirect_methods was added.
This option is a comma-delimited, case-insensitive list of SIP methods
for which SIP 3XX redirect responses are followed. An alembic upgrade
script has been added for adding this new option to the Asterisk
database.
taskprocessors: Improve logging and add new cli options
New CLI command has been added -
core show taskprocessor name
ccss: Add option to ccss.conf to globally disable it.
A new "enabled" parameter has been added to ccss.conf. It defaults
to "yes" to preserve backwards compatibility but CCSS is rarely used so
setting "enabled = no" in the "general" section can save some unneeded channel
locking operations and log message spam. Disabling ccss will also prevent
the func_callcompletion and chan_dahdi modules from loading.
Makefile: Add module-list-* targets.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
app_mixmonitor: Add 's' (skip) option to delay recording.
This change introduces a new 's()' (skip) option to the MixMonitor
application. Example:
MixMonitor(${UNIQUEID}.wav,s(3))
This skips recording for the first 3 seconds before writing audio to the file.
Existing MixMonitor behavior remains unchanged when the 's' option is not used.
app_queue.c: Only announce to head caller if announce_to_first_user
When announce_to_first_user is false, no announcements are played to the head caller
Upgrade Notes:
res_geolocation: Fix multiple issues with XML generation.
Geolocation: In order to correct bugs in both code and
documentation, the following changes to the parameters for GML geolocation
locations are now in effect:
The documented but unimplemented crs (coordinate reference system) element
has been added to the location_info parameter that indicates whether the 2d
or 3d reference system is to be used. If the crs isn't valid for the shape
specified, an error will be generated. The default depends on the shape
specified.
The Circle, Ellipse and ArcBand shapes MUST use a 2d crs. If crs isn't
specified, it will default to 2d for these shapes.
The Sphere, Ellipsoid and Prism shapes MUST use a 3d crs. If crs isn't
specified, it will default to 3d for these shapes.
The Point and Polygon shapes may use either crs. The default crs is 2d
however so if 3d positions are used, the crs must be explicitly set to 3d.
The geoloc show gml_shape_defs CLI command has been updated to show which
coordinate reference systems are valid for each shape.
The pos3d element has been removed in favor of allowing the pos element
to include altitude if the crs is 3d. The number of values in the pos
element MUST be 2 if the crs is 2d and 3 if the crs is 3d. An error
will be generated for any other combination.
The angle unit-of-measure for shapes that use angles should now be included
in the respective parameter. The default is degrees. There were some
inconsistent references to orientation_uom in some documentation but that
parameter never worked and is now removed. See examples below.
Examples...
The threadpool_* options in pjsip.conf have now
been deprecated though they continue to be read and used.
They have been replaced with taskpool options that give greater
control over the underlying taskpool used for PJSIP. An alembic
upgrade script has been added to add these options to realtime
as well.
app_directed_pickup.c: Change some log messages from NOTICE to VERBOSE.
In an effort to reduce log spam, two normal progress
"pickup attempted" log messages from app_directed_pickup have been changed
from NOTICE to VERBOSE(3). This puts them on par with other normal
dialplan progress messages.
Developer Notes:
ccss: Add option to ccss.conf to globally disable it.
A new API ast_is_cc_enabled() has been added. It should be
used to ensure that CCSS is enabled before making any other ast_cc_* calls.
chan_websocket: Add ability to place a MARK in the media stream.
Apps can now send a MARK_MEDIA command with an optional correlation_id parameter to chan_websocket which will be placed in the
media frame queue. When that frame is dequeued after all intervening media
has been played to the core, chan_websocket will send a MEDIA_MARK_PROCESSED event to the app with the same correlation_id
(if any).
chan_websocket: Add capability for JSON control messages and events.
The chan_websocket plain-text control and event messages are now
deprecated (but remain the default) in favor of JSON formatted messages.
See https://docs.asterisk.org/Configuration/Channel-Drivers/WebSocket for
more information.
A "transport_data" parameter has been added to the
[p]Added Anubis to the Active Duty Map Pool[/p][/*]
[p]Removed Train from the Active Duty Map Pool[/p][/*]
[p][/p][p]\[ COMPETITIVE ][/p]
[p]Adjusted underlying per-map competitive matchmaking rank values. Existing per-map competitive Skill Groups have been expired, and will be displayed again once the player obtains the required number of wins[/p][/*]
[p][/p][p]\[ GAMEPLAY ][/p]
[p]Minor adjustments to the MP7 and MP5-SD:[/p]
[p]Slightly increased damage[/p][/*]
[p]Slightly reduced damage fall-off[/p][/*]
[p]Reduced price by $100.[/p][/*]
[/*]
[p]Reduced price of the PP-Bizon by $100.[/p][/*]
[p]Jump changes:[/p]
[p]Landing time is now calculated with subtick precision[/p][/*]
[p]Jumping and landing no longer affect stamina. The landing speed penalty is now a simple function of landing time[/p][/*]
[p]Any jump press within sv_bhop_time_window centered on the landing time that hasn't been penalized by sv_jump_spam_penalty_time will be treated as a successful bunnyhop[/p][/*]
[p]Legacy jump behavior can be restored on private servers with sv_legacy_jump[/p][/*][/*]
[p]Map Guides can now be loaded in online games of casual and retakes (via the ESC menu)[/p][/*][p][/p][p]\[ SOUND ] [/p]
[p]Reduced audio output latency[/p][/*]
[p]Higher fidelity knife draw and inspect sounds[/p][/*]
[p]Weapon, knife and utility draw sounds no longer overlap when switching quickly between them[/p][/*]
[p]Knife impact sounds are now unique based on primary fire or alt fire swings as well as front and rear attacks. This reflects the different damage amounts dealt with each attack [/p][/*]
[p]Ambient sounds no longer restart from the beginning when transitioning between zones[/p][/*][p][/p][p]\[ WEEKLY CARE PACKAGE ][/p]
[p]Added two all-new weapon collections to the Weekly Care Package drop list: Harlequin, Achroma[/p][/*]
[p]Removed four weapon collections from the Weekly Care Package drop list: Safehouse, Dust 2, 2018 Nuke Collection, and the 2018 Inferno Collection[/p][/*][p][/p][p]\[ ARMORY ][/p]
[p]Added a new Limited Edition Item: the AK47 | Aphrodite[/p][/*][p][/p][p]\[ MISC ][/p]
[p]Increased material fidelity on some of the base guns:[/p]
[p]Ak47[/p][/*]
[p]Aug[/p][/*]
[p]AWP[/p][/*]
[p]Berettas[/p][/*]
[p]Deagle[/p][/*]
[p]Galil[/p][/*]
[p]Mac-10[/p][/*]
[p]MP7[/p][/*]
[p]P250[/p][/*]
[p]Tec9[/p][/*]
[p]USP-S[/p][/*]
[p]Bizon[/p][/*]
[p]Cz75a[/p][/*]
[p]Famas[/p][/*]
[p]MP9[/p][/*][/*]
[p]Changed voice status behavior to always show a mic for local player if mic is open [/p][/*]
[p]Fixed a bug related to Deathcam intersection[/p][/*]
[p]Fixed some cases where the player would collide with internal edges while sliding along a ramp in surf mode[/p][/*]
[p]Improved the resolution of the PVS for some static level geometry[/p][/*]
[p]Fixed some small interpenetrations in Butterfly Knife animations[/p][/*]
[p]Fixed a case where blood decals weren't appearing[/p][/*][p][/p][p]\[ MAP SCRIPTING ][/p]
[p]Fixed a bug where activator was sometimes incorrect for func_door outputs OnOpen, OnFullyOpen, OnClose, and OnFullyClosed[/p]
there is a discord server with an @everyone in case of future important updates, such as vulnerabilities (most recently 2025-09-07)
🧪 new features
send-message-to-serverlog now also available as url-parameter ?smsg=foo6dcb1ef
option smsg configures which HTTP-methods to allow; can be set to GET,POST but default is only POST because GET is dangerous (CSRF)
🩹 bugfixes
#1227dillo was not able to login because dillo is more standards-compliant than every other browser (nice) b4df8fa
a web-scraper which got banned for making malicious requests could remain banned for one request longer than intended (wait why did I fix this) ba67b27
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
Highlights in OpenWrt 25.12
OpenWrt 25.12.0-rc3 incorporates over 4300 commits since branching the previous OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc3 for the full changelog.
General changes
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with OpenWrt 25.12.
Switch package manager from opkg to apk
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk is still maintained, the OpenWrt opkg fork was not maintained any more.
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
Automatically rebuild firmware images with all currently installed packages
Preserve system configuration during upgrades
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell history is preserved
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem.
Benefits:
Command history is no longer lost between logins
No unnecessary writes to flash storage by default
For users who prefer persistent history storage, this behavior can be changed by editing: /etc/profile.d/busybox-history-file.sh
⚠️ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
Integration of video feed
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
Wi-Fi scripts in ucode
The wifi scripts were rewritten in ucode.
Target changes
Extend realtek target with support for more switch SoCs like 10G Ethernet switches.
Extend qualcommax target with support for ipq50xx and ipq60xx SoCs.
Added siflower target for Siflower SF21A6826/SF21H8898 SoCs
Added sunxi/arm926ejs subtarget for Allwinner F1C100/200s SoCs
Many new devices added
OpenWrt 25.12 supports over 2180 devices. Support for over 160 new devices was added in addition to the device support by OpenWrt 24.10.
Core components update
Core components have the following versions in 25.12.0-rc3:
Updated toolchain:
musl libc 1.2.5
glibc 2.41
gcc 14.3.0
binutils 2.44
Updated Linux kernel
6.12.66 for all targets
main packages:
cfg80211/mac80211 from kernel 6.18.0
hostapd master snapshot from August 2025
dnsmasq 2.91
dropbear 2025.89
busybox 1.37.0
In addition to the listed applications, many others were also updated.
Upgrading to 25.12
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.
Sysupgrade from 23.05 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.
Bananapi BPI-R4: Interfaces eth1 was renamed to sfp-lan or lan4 and the interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration.
Scratch installs/upgrades
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade options
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Firmware Selector - an online builder that requires you to manually supply it with the packages you wish to have installed. This package list is sent to the ASU server, and a new custom device image is created containing those packages. You may then download and install the image in LuCI Backup/Flash Firmware, but for this you would enable "Keep settings..."
Luci Attended Sysupgrade - the web interface to the ASU server. This tool allows you to choose a new OpenWrt version, then collects the names of the packages on your device and sends them up to the ASU server. LuCI ASU then downloads the created image directly to your device and allows you to install it, without having to do any of the bookkeeping tasks involved with using the Firmware Selector.
owut - a command line package that does the same job as LuCI ASU, but provides more diagnostics and better visibility into what's happening at the various steps before and during the build process.
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg:
Note that you can install one or the other, or both together, they are completely independent packages.
Upgrades with Firmware Selector
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure about which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
Upgrades with LuCI Attended Sysupgrade
The LuCI web interface should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure about something, go to the LuCI Attended Sysupgrade support thread and ask.
Upgrades with owut
If you choose to use owut, the fact that it's a command line program means you'll need a little more explanation regarding best practices. In any situation, it's always safe to do a check to see what's going on.
$ owut check --verbose --version-to 25.12
... a lot of output ...
This check should show you all the details of what this upgrade entails with regards to the packages available, and will point out any issues with package versions and so on.
Assuming the results of the check look good, you can simply do an upgrade next.
$ owut upgrade --verbose --version-to 25.12
... even more output ...
If you are unsure of anything you see in the check, during the upgrade, or simply have questions, jump on over to the owut support thread on the forum and ask.
Known issues
Users of Zyxel EX5601-T0 devices need to check their WAN interfaces as port was renamed from eth1 to wan.
Microchip LAN969x devices are missing the network driver, so no network ports work.
The Stable channel has been updated to 144.0.7559.96/.97 for Windows/Mac and 144.0.7559.96 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log.
Security Fixes and Rewards
Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.
This update includes 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.
[TBD][473851441] High CVE-2026-1220: Race in V8. Reported by @p1nky4745 on 2026-01-07
We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.
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.
26.1 Snapshot 4 (known as 26.1-snapshot-4 in the launcher) is the fourth snapshot for Java Edition 26.1, released on January 20, 2026, which changes the models of baby horses, donkeys, and mules, as well as zombie and skeleton horses, adds new tags, and fixes bugs.
Full changelog: https://minecraft.wiki/Java_Edition_26.1-snapshot-4
It’s time to celebrate what we’ve built together, and get excited about what’s coming next – at State of the Open Home, our annual look at how we’re championing privacy, choice, and sustainability in the smart home. And this year, we’re doing something new: inviting you to be part of the action in our audience! 🎉
That’s right, you don’t have to watch from home – you can join us live in Utrecht, the Netherlands, on Wednesday, April 8.
This year’s theme: Building in the open
Building in the open has always been at the heart of what the Open Home Foundation does, across Home Assistant and other projects. This year, we’re taking it to the next level – shining a spotlight on the transparency and collaboration that sets this community apart.
We’re talking open roadmaps, honest conversations about the way we work and the challenges we face, and how we solve them together. Plus, we’ll be showcasing what our community achieved in 2025, giving you a look at what’s ahead – and asking you to help shape it.
What to expect
We’re putting the final touches on the program (watch this space!) – but here’s a taste of what’s in store:
Celebrate all we’ve achieved together in 2025
See what’s ahead for Home Assistant and the wider ecosystem
Connect with fellow Open Home advocates and contributors in person
Have your say in the discussions guiding the future of the Open Home
And that’s just the start. Expect special guests, a few surprises, and the kind of positive energy you only get when this community gathers in one room ⚡.
Tickets available soon!
Limited spots will be available for our live audience in Utrecht, the Netherlands. Tickets will be available from early February – and they’ll go fast, so stay tuned for details! We’ll also be livestreaming globally for those who can’t make it in person.
We are pleased to announce the latest stable release of Jellyfin, version 10.11.6! This minor release brings several bugfixes to improve your Jellyfin experience. As always, please ensure you take a full backup before upgrading!
You can find more details about and discuss this release on our forums.
Changelog (8)
🏗️ Enhancements
Add default font family for fallback [PR #7499], by @thornbill
Restore back button in experimental layout for apps [PR #7500], by @thornbill
We are pleased to announce the latest stable release of Jellyfin, version 10.11.5! This minor release brings several bugfixes to improve your Jellyfin experience. As always, please ensure you take a full backup before upgrading!
You can find more details about and discuss this release on our forums.
Log in
