New release candidate: 2.0.0rc6

Slightly delayed thanks to the first cold of the season 🤧, here’s the sixth release candidate for the upcoming 2.0.0 release with some more fixes of regressions and some long standing newly discovered bugs, as well as one backwards compatiblity fix for 3rd party plugins:

✨ Improvements

Gcode Viewer Plugin

  • Support old loadFile signature on view model as apparently used by third party plugins out there (e.g. UICustomizer)

🐛 Bug fixes

Core

  • PR#5450: Reject NaN & Inf when saving file metadata
  • #5454 (regression): Fix wrong check inside local storage that under very limited circumstances could lead to a limited path traversal vulnerability on the download API endpoint.
  • #5466 (regression): Fix metadata refresh on file upload. A cache was not being emptied correctly.
  • (regression) Handle broken analysis, statistics & history metadata on files instead of just ignoring the whole file for the file list. Try to transparently sanitize data were needed, remove completely invalid data as needed.
  • (regression) Fix a race condition causing the PrintFailed event to be sent with the wrong payload.
  • (regression) Properly handle progress reporting for an unset job.
  • Replace use of deprecated inspect.getargspec (backported from PR#5464).
  • Fix logging of invalid wizard versions (backported from PR#5464).

Core UI

  • Improve resilience against various runtime data issues.

Health Check Plugin

  • (regression) Make storage thresholds available again on the settings API.

Serial Connector

  • (regression) Gracefully handle unknown file reported by printer as selected for printing.
  • Fix wrong seek signature for streaming opened file handles (backported from PR#5464).

Docs

  • PR#5449: Fix FileDestinations.SDCARD notes in migration guide
  • Fix the reason for various warnings

For heads-ups, highlights and fancy pictures, please see the earlier post about 2.0.0rc1.

You can find the full changelog and release notes as usual on GitHub.

Special thanks to everyone who contributed to this release candidate and provided full, analyzable bug reports, you help making the next release as stable as possible! And of course also thank you to everyone who helped fund the development that went into this release candidate!

A special Thank You! to this fine person for their PRs!

@jacopotediosi
@jacopotediosi

As the past RCs have shown me that a lot of people appear to be unaware of this: Please do not install this RC if you expect a fully stable version. It is not a stable release, it is a release candidate: severe bugs may occur, and they might be bad enough that they make a manual downgrade to an earlier version necessary - maybe even from the command line.

You should feel comfortable with and capable of possibly having to do this before installing an RC.

If you want to and can help test this release candidate, you can find information on how to switch to the "Release Candidates" release channel in this guide if not already done (also linked below).

Please provide feedback on this RC. For general feedback you can use this ticket on the tracker. The information that everything works fine for you is also valuable feedback 😄. For bug reports please follow How to file a bug report - I need logs and reproduction steps to fix issues, not just the information that something doesn't work so make sure to fill out all fields of the issue template.

While testing the release candidate, please take a closer look at these things:

  • Proper behaviour when using the included web interface as well as any third party clients at your disposal.

  • Printing via serial connection.

  • Managing files on your printers storage via a serial connection.

  • Blocklisted serial ports and/or baud rates are properly migrated to the serial connector (one per line, not comma-separated).

  • If your printer’s disconnected state happens to be “after error”, please report back on which connector you used and what the reported error is.

  • If you have a Klipper/Moonraker based printer available: can you use it through OctoPrint when you install the Moonraker Connector (work in progress)?

  • If you have a Bambu based printer available: can you use it through OctoPrint when you install the Bambu Connector (work in progress)?

Thanks!

Depending on the feedback regarding this version I'll look into fixing any observed regressions and bugs and pushing out a follow-up version as soon as possible and necessary.

Discuss!

Author
Gina Häußge
Published
07 Oct 2026
Category
Release