LoginSign Up
← Back to all sparks
O

OctoPrint

INFRA · APIS
Velocity5.0

Web interface for controlling and monitoring 3D printers

octoprint.org ↗

OctoPrint 2.0 is on its seventh release candidate, still with no final date.

3d-printingconnector-architecturebreaking-changesrelease-candidatesplugin-ecosystem
◆Current state
OctoPrint 2.0 makes serial one connector among several, including Moonraker and Bambu, and removes deprecated plugin APIs. Release candidates have arrived every few weeks since April: rc5 in August fixed config and schema regressions, and rc6 and rc7 in October carried only the standard warning that a candidate may need a manual downgrade.
◆Where it's heading
The 2.0 line is in a long stabilisation, with each candidate fixing regressions and asking testers to cover the new connectors. The thin notes on rc6 and rc7 suggest the remaining changes are small.
◆Prediction
A 2.0.0 final is likely within a few candidates; the exact date is unclear from the entries.

◆Recent moves

  1. 15d ago

    OctoPrint 2.0.0 release candidate 7

    The seventh release candidate for OctoPrint 2.0.0, with the usual warning that RCs may require a manual downgrade. Another step toward the 2.0 final.

    View source ↗
  2. 28d ago

    2.0.0rc6: another release candidate for OctoPrint 2.0

    Another release candidate for OctoPrint 2.0, with the usual warning that it may need a manual downgrade.

    View source ↗
  3. 2mo 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 ↗
  4. 3mo 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 ↗
  5. 4mo 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 ↗
  6. 5mo 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 ↗