This release contains the following fixes and changes:
there is a discord server with an @everyone in case of future important updates, such as vulnerabilities (most recently 2025-09-07)
Log inurlform global-option was changed to get
connection:close (don't reuse tcp/uds connections), as giving each client a fresh socket helps avoid all such issues e1eff21 b4fddbc
The Asterisk Development Team would like to announce
the release of asterisk-23.2.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/23.2.0
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 23.2.0
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
The category name in the chan_websocket.conf.sample file was
incorrect. It should be "global" instead of "general".
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.
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.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-leveldevice, person or tuple elements.device_id which sets the content of the <deviceID> element.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.
New CLI command has been added -
core show taskprocessor name
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.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
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.
When announce_to_first_user is false, no announcements are played to the head caller
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:
crs (coordinate reference system) element2d3d reference system is to be used. If the crs isn't valid for the shape2d crs. If crs isn't2d for these shapes.3d crs. If crs isn't3d for these shapes.2d3d positions are used, the crs must be explicitly set to 3d.geoloc show gml_shape_defs CLI command has been updated to show whichpos3d element has been removed in favor of allowing the pos element3d. The number of values in the pos2d and 3 if the crs is 3d. An errordegrees. There were someorientation_uom in some documentation but that location_info = shape="Sphere", pos="39.0 -105.0 1620", radius="20"
location_info = shape="Point", crs="3d", pos="39.0 -105.0 1620"
location_info = shape="Point", pos="39.0 -105.0"
location_info = shape=Ellipsoid, pos="39.0 -105.0 1620", semiMajorAxis="20"
semiMinorAxis="10", verticalAxis="0", orientation="25 degrees"
pidf_element_id = ${CHANNEL(name)}-${EXTEN}
device_id = mac:001122334455
Set(GEOLOC_PROFILE(pidf_element_id)=${CHANNEL(name)}/${EXTEN})
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.
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.
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.
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).
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 Asterisk Development Team would like to announce
the release of asterisk-22.8.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/22.8.0
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 22.8.0
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
The category name in the chan_websocket.conf.sample file was
incorrect. It should be "global" instead of "general".
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.
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.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-leveldevice, person or tuple elements.device_id which sets the content of the <deviceID> element.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.
New CLI command has been added -
core show taskprocessor name
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.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
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.
When announce_to_first_user is false, no announcements are played to the head caller
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:
crs (coordinate reference system) element2d3d reference system is to be used. If the crs isn't valid for the shape2d crs. If crs isn't2d for these shapes.3d crs. If crs isn't3d for these shapes.2d3d positions are used, the crs must be explicitly set to 3d.geoloc show gml_shape_defs CLI command has been updated to show whichpos3d element has been removed in favor of allowing the pos element3d. The number of values in the pos2d and 3 if the crs is 3d. An errordegrees. There were someorientation_uom in some documentation but that location_info = shape="Sphere", pos="39.0 -105.0 1620", radius="20"
location_info = shape="Point", crs="3d", pos="39.0 -105.0 1620"
location_info = shape="Point", pos="39.0 -105.0"
location_info = shape=Ellipsoid, pos="39.0 -105.0 1620", semiMajorAxis="20"
semiMinorAxis="10", verticalAxis="0", orientation="25 degrees"
pidf_element_id = ${CHANNEL(name)}-${EXTEN}
device_id = mac:001122334455
Set(GEOLOC_PROFILE(pidf_element_id)=${CHANNEL(name)}/${EXTEN})
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.
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.
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.
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).
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 Asterisk Development Team would like to announce
the release of asterisk-20.18.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/20.18.0
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 20.18.0
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
The category name in the chan_websocket.conf.sample file was
incorrect. It should be "global" instead of "general".
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.
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.
Geolocation: Two new optional profile parameters have been added.
pidf_element_id which sets the value of the id attribute on the top-leveldevice, person or tuple elements.device_id which sets the content of the <deviceID> element.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.
New CLI command has been added -
core show taskprocessor name
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.
Try "make module-list-deprecated" to see what modules
are on their way out the door.
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.
When announce_to_first_user is false, no announcements are played to the head caller
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:
crs (coordinate reference system) element2d3d reference system is to be used. If the crs isn't valid for the shape2d crs. If crs isn't2d for these shapes.3d crs. If crs isn't3d for these shapes.2d3d positions are used, the crs must be explicitly set to 3d.geoloc show gml_shape_defs CLI command has been updated to show whichpos3d element has been removed in favor of allowing the pos element3d. The number of values in the pos2d and 3 if the crs is 3d. An errordegrees. There were someorientation_uom in some documentation but that location_info = shape="Sphere", pos="39.0 -105.0 1620", radius="20"
location_info = shape="Point", crs="3d", pos="39.0 -105.0 1620"
location_info = shape="Point", pos="39.0 -105.0"
location_info = shape=Ellipsoid, pos="39.0 -105.0 1620", semiMajorAxis="20"
semiMinorAxis="10", verticalAxis="0", orientation="25 degrees"
pidf_element_id = ${CHANNEL(name)}-${EXTEN}
device_id = mac:001122334455
Set(GEOLOC_PROFILE(pidf_element_id)=${CHANNEL(name)}/${EXTEN})
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.
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.
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.
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).
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
there is a discord server with an @everyone in case of future important updates, such as vulnerabilities (most recently 2025-09-07)
?smsg=foo 6dcb1ef
smsg configures which HTTP-methods to allow; can be set to GET,POST but default is only POST because GET is dangerous (CSRF)?ls was still a bit jank 0a3a807
Hi,
The OpenWrt community is proud to announce the third release candidate of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker.
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.
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with OpenWrt 25.12.
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
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.
The attended sysupgrade LuCI application is now installed by default.
ASU allows devices to:
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 command history is now preserved across sessions by storing it in a RAM-backed filesystem.
Benefits:
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.
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
The wifi scripts were rewritten in ucode.
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 have the following versions in 25.12.0-rc3:
In addition to the listed applications, many others were also updated.
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.
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 (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:
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:
$ opkg update
$ opkg install luci-app-attendedsysupgrade
$ opkg install owut
Note that you can install one or the other, or both together, they are completely independent packages.
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.
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.
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.
eth1 to wan.Full release notes and upgrade instructions are available at
https://openwrt.org/releases/25.12/notes-25.12.0-rc3
In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/25.12/notes-25.12.0-rc3#known_issues
For a detailed list of all changes since 25.12.0-rc2, refer to
https://openwrt.org/releases/25.12/changelog-25.12.0-rc3
To download the 25.12.0-rc3 images, navigate to:
https://downloads.openwrt.org/releases/25.12.0-rc3/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org?version=25.12.0-rc3
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
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.
Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.
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.
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.
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.
We’re putting the final touches on the program (watch this space!) – but here’s a taste of what’s in store:
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 ⚡.
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.
Visit our new State of the Open Home website to learn more, and be sure to follow us on Fosstodon, Bluesky, Instagram or Facebook so you don’t miss the ticket drop!
📅 Mark your calendars now: Wednesday, April 8, Utrecht, the Netherlands.
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.
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.
We are pleased to announce the latest stable release of Jellyfin, version 10.11.4! 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.
We are pleased to announce the latest stable release of Jellyfin, version 10.11.3! 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.
We are pleased to announce the latest stable release of Jellyfin, version 10.11.2! 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.
We are pleased to announce the latest stable release of Jellyfin, version 10.11.1!
This minor release brings several bugfixes to improve your Jellyfin experience.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
You can find more details about and discuss this release on our forums.
We are pleased to announce the latest stable release of Jellyfin, version 10.11.0!
This major release brings many new features, improvements, and bugfixes to improve your Jellyfin experience.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
WARNING: There are very important release notes to review before upgrading! Please find all the details in our blog post on the release.
You can find more details about and discuss this release on our forums.
toast and confirm to TypeScript [PR #5219], by @StableCrimson@types/react-lazy-load-image-component to dev dependencies [PR #6419], by @tomheaton
We are pleased to announce the ninth release candidate preview release of Jellyfin 10.11.0!
This is a preview release, intended for those interested in testing 10.11.0 before it's final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
Please see the WIP release notes here for now: https://notes.jellyfin.org/v10.11.0_features
PLEASE READ THOSE NOTES THOROUGHLY BEFORE UPGRADING; current RC users should have a seamless upgrade. If you have any questions, please ask in our Matrix chat.
This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.
10.11.0-rc9 or preview tags.Full Changelog: v10.11.0-rc8...v10.11.0-rc9
Previous RC Changelogs: https://github.com/jellyfin/jellyfin/releases/tag/v10.11.0-rc7 [RC8 had no changes]
We are pleased to announce the eighth release candidate preview release of Jellyfin 10.11.0!
This is a preview release, intended for those interested in testing 10.11.0 before it's final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
Please see the WIP release notes here for now: https://notes.jellyfin.org/v10.11.0_features
PLEASE READ THOSE NOTES THOROUGHLY BEFORE UPGRADING; current RC users should have a seamless upgrade. If you have any questions, please ask in our Matrix chat.
CRITICAL BUG FIX - DO NOT RUN RC7, run this instead! Upgrading from <= RC5 to RC7 will cause a library breakage (#14888, #14894) that this RC8 fixes.
This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.
10.11.0-rc8 or preview tags.No changes.
Previous RC Changelogs: https://github.com/jellyfin/jellyfin/releases/tag/v10.11.0-rc7
We are pleased to announce the sixth release candidate preview release of Jellyfin 10.11.0!
This is a preview release, intended for those interested in testing 10.11.0 before it's final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
Please see the WIP release notes here for now: https://notes.jellyfin.org/v10.11.0_features
PLEASE READ THOSE NOTES THOROUGHLY BEFORE UPGRADING; current RC users should have a seamless upgrade, though you should rescan all libraries and run a PeopleRefresh after updating. If you have any questions, please ask in our Matrix chat.
This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.
10.11.0-rc7 or preview tags.Full Changelog: v10.11.0-rc6...v10.11.0-rc7
Full Changelog: v10.11.0-rc5...v10.11.0-rc6
Full Changelog: v10.11.0-rc4...v10.11.0-rc5
Full Changelog: v10.11.0-rc3...v10.11.0-rc4
Full Changelog: v10.11.0-rc2...v10.11.0-rc3
Full Changelog: v10.11.0-rc1...v10.11.0-rc2
@types/react-lazy-load-image-component to dev dependencies by @tomheaton in #6419toast and confirm to TypeScript by @StableCrimson in #5219Full Changelog: v10.10.7...v10.11.0-rc1
P.S.: if you enjoy Dopamine, please consider donating with PayPal or buying me a coffee. Thank you so much!
First release!
Highlights:
Enjoy the music!
P.S.: if you enjoy Dopamine, please consider donating with PayPal or buying me a coffee. Thank you so much!
Fix #776: Artists - Strange artist name bugs
