LoginSign Up
← Back to all sparks
O

OctoPrint

INFRA · APIS
Velocity2.5

Web interface for controlling and monitoring 3D printers

octoprint.org ↗

OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.

3d-printingconnector-architecturebreaking-changesrelease-candidatesplugin-ecosystem
◆Current state
The 2.0 candidate line reaches rc5, still stabilising rather than adding. This cut is bug and regression fixes: config subcommand options being ignored, chamber defaults missing from the schema, a deprecated babel-polyfill dependency slowing the UI, discovery data re-exposed for third-party clients, and doubled Error events from the serial connector. The testing asks now explicitly cover the Moonraker and Bambu connectors, alongside the serial migration checks that have been in every candidate since rc2.
◆Where it's heading
Serial is being demoted from the way OctoPrint talks to a printer to one implementation of a connector interface, which is the structural precondition for supporting printers that speak something else — and the rc5 asks name Moonraker and Bambu connectors as installable things to try, not future plans. The candidates themselves are converging: rc5's fixes are regressions in work introduced by earlier candidates rather than new migration surface. The unexplained error states the maintainer keeps flagging remain the open item holding the line short of a final.
◆Prediction
Expect further candidates until the disconnected-after-error reports resolve, since that is the one issue called out across multiple RCs. A 2.0.0 final should follow once the connector migration stops producing regressions, with the Moonraker and Bambu connectors shipping as separate installable plugins rather than in core.

◆Recent moves

  1. 23d ago

    2.0.0rc5 fixes regressions and asks for Moonraker and Bambu testing

    A stabilising candidate: config subcommand options that were being ignored, a schema gap that made the frontend resend every temperature profile on each save, a deprecated polyfill removed from the UI, and two regressions repaired in discovery and the serial connector. The notable part is not the fixes but the testing asks, which now name the Moonraker and Bambu connectors as things to install and try — the connector architecture being exercised on non-serial printers for the first time.

    View source ↗
  2. 2mo ago

    2.0.0rc4 continues serial connector migration testing

    The fourth candidate keeps the same testing focus: third-party clients against the web interface, printing and file management over serial, and correct migration of blocklisted ports and baud rates into the serial connector. Iteration on the 2.0 migration rather than new ground.

    View source ↗
  3. 2mo ago

    2.0.0rc3 repeats the connector and serial-storage test asks

    Substantively identical testing guidance to rc2, including the request to report which connector was in use when a printer reports a disconnected-after-error state. The cumulative RC notes make the incremental changes invisible from the feed alone.

    View source ↗
  4. 3mo ago

    2.0.0rc2 adds the serial connector migration checks

    Where the blocklisted-port and baud-rate migration into the serial connector first appears in the testing checklist, alongside the connector-specific error reporting request. It marks the point where the connector abstraction became something users had to verify.

    View source ↗
  5. 4mo ago

    2.0.0rc1 opens the 2.0 line and removes deprecated APIs

    ⚡ SPARK

    The first candidate of the 2.0 line, and where the breakage is declared: deprecated interfaces are removed, plugins are expected to break, and a recovery page exists to restart in safe mode when they do. Klipper and Moonraker printers are named in the testing asks, which is the clearest signal of where the connector work is heading.

    View source ↗