New release candidate: 2.0.0rc2

This second release candidate for the upcoming 2.0.0 release fixes several regressions that were reported with the first one, as well as some newly found bugs. It also improves on newly added functionality and introduces two new version check options for the Software Update Plugin:

✨ Improvements

Core

  • #5385: Add migration for terminal filters to new filter prefixes. Also improve migration guide accordingly.

Core UI

  • Add option to the sidebar file manager’s menu to (recursively) refresh the current storage’s & path’s thumbnails (if supported).

Healthcheck Plugin

  • Add health check hint for unusable gcode_thumbnail_tool with link to the FAQ entry.

Software Update Plugin

  • Add support for forgejo_release and forgejo_commit version check types, which enable version checks against Forgejo code forges such as Codeberg. For Codeberg specifically, there’s also codeberg_release and codeberg_commit which internally gets remapped to forgejo_* with the correct forge parameter.

Docs

  • Add more examples to the migration guide and deprecation list.
  • Add docs for octoprint.util.version.

🐛 Bug fixes

Core

  • #5377 (regression): Fix evaluation of print parameter on upload API.
  • #5379 (regression): Fix deselection of current print job not working.
  • #5380 (regression): Allow None filament weight in /api/job response.
  • #5390 (regression): Gracefully handle unavailability of gcode_thumbnail_tool due to missing OS dependencies.
  • #5393 (regression): Fix file/folder move from root directory.
  • (regression) Fix file commands on storage root.
  • Fix repo file links still pointing to master vs main.

Core UI

  • #5375 (regression): Fix broken availability logic on connection button.
  • #5384 (regression): Fix “Update User” button in access settings.
  • #5386 (regression): Fix some template permission checks broken during removal of deprecated code.

Plugin Manager

  • #5382: Fix support for pip VCS URL schemes as archive URL.

Serial Connector

  • Fix error handling in serial detection. A serial error raised during detection should not cause the whole detection workflow to stop, but rather just switch to the next test option.

Software Update Plugin

  • #5400: Fix default tracked branch for OctoPrint commit tracking, was still pointing to master instead of main.
  • Fix default user for OctoPrint release check, was still pointing to foosel instead of OctoPrint (though was also redirected).

Tracking

  • Fix tracking of printer_connected event if the current connector doesn’t send a FirmwareData event (prevented tracking of BambuConnector use).

Docs

  • #5394: Fix an example still referring to a removed function.

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 these 2 fine people for their PRs!

@jacopotediosi
@jacopotediosi
@jneilliii
@jneilliii

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
19 May 2026
Category
Release