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 entire feed is the 2.0.0 release candidate series — four RCs between April and July 2026, no stable tag. The testing asks reveal what changed underneath: blocklisted serial ports and baud rates are migrated into a serial connector, testers are asked which connector they used when a printer lands in an error state, and rc1 raises Klipper and Moonraker printers directly. Each RC restates the same release-candidate warnings, so the notes read as testing instructions rather than a changelog.
◆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. The cost is deliberate: rc1 removes deprecated APIs, warns that plugins will break, and points users at a recovery page to restart in safe mode. A maintainer running a long public RC cycle on a single-maintainer project is managing that breakage rather than rushing past it.
◆Prediction
Expect further RCs until the connector migration stops producing reports, with the plugin ecosystem's readiness — not the core code — deciding when 2.0.0 goes stable.

◆Recent moves

  1. 23d 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 ↗
  2. 1mo 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 ↗
  3. 2mo 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 ↗
  4. 3mo 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 ↗