This release is a canary release intended to be used for testing.
This version is a bugfix release for some issues discovered with the previous canary build.
I want to thank you for your diligence and user patients with Duplicati. FWIW, it’s been a digital comfort I’ve gratefully advantaged and taken for granted for many years. Thanks! 
Seconded!! Many thanks!
Cosmetic issue, when I try to use the menu for the last job listed, so the list is at the bottom, then menu cannot be scrolled:
I greatly appreciate using Smart Backup Retention, but hope I’ll never need the “wayback” reach it provides. Good to know it’s there!
Are the “Use old UI” and “Use new UI” supposed to control future tabs, including by TrayIcon?
It seems to be one-way, with old UI being sticky. Undocumented theme.html is a temporary fix.
I’m in Edge developer tools, watching the default-client cookie (refreshing as appropriate).
As a side note, there’s also a default-theme cookie hanging around. Not sure if that matters.
Wasn’t the whole summer/winter time thing meant to have been resolved with this next-gen version Duplicati?
Had to adjust all my backups yesterday by an hour after the clocks when back here 
The announcement said below, and my good test results from Spring 2025 were posted later.
My Fall 2025 1 hour move off DST is coming up Sunday Nov. 2 at 2 A.M. First test that way.
No idea what developer testing (e.g. in VM) was done. If it matters, my jobs run near 7 A.M.
Change off DST fell back an hour in Duplicati. I had hoped dailies would hold as in Spring.
On night before, my 7 AM-ish daily runs were forecasting 6-ish. On next day, next are too.
I saved some server databases if they would help, but maybe dev could test this on a VM?
I’ll probably move the jobs to their correct time soon unless somebody gives reason not to.
7:50 OneDrive backup ran at 6:50 (so Duplicati did 1 day interval as 24 hours – no adjust).
7:20 Backblaze backup ran at 6:20.
In better news:
I set up a job to run hourly, starting 30 minutes before loss of DST. I expected a double run,
because 2 fell back to 1, so 1:30 happened again but on standard time, not daylight saving:
2025-11-02 01:30:01 -04 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Backup has started
2025-11-02 01:30:00 -05 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Backup has started
2025-11-02 02:30:03 -05 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Backup has started