OctoPrint 2.0.0 is coming soon!

Yes, you read this right, the next version of OctoPrint won’t be 1.12.0 but actually 2.0.0!

When I started working on this release back in November of 2024, the #1 goal was to finally make it possible to add support for other printer interfaces than a serial connection through plugins. This has been a major goal of mine since 2015 now and I had to throw away two or three attempts at achieving this as they turned out to be too complex, too impractical or just didn’t work at all. Thankfully, this time the stars aligned, the architectural approach held, and it finally worked out 🥳. And with the work-in-progress Moonraker Connector Plugin and Bambu Connector Plugin there are already two plugins being prepared that will make OctoPrint and its Plugin Ecosystem compatible to a ton of recent printers!

I also turned the printer storage into a fully supported native storage inside of OctoPrint, opened up the storage support to allow for further options to be added by plugins, added native thumbnail support, cross-storage transfers, multi-storage support on the frontend, a proper print job data model and a ton of other stuff.

However, getting all of this to work required quite a lot of internal changes. While I did my best to keep things backwards compatible, including adding versioning support for the REST API and several compatibility layers, I couldn’t be 100% sure that no breaking changes made it into the upcoming release.

I therefore decided to finally increase the major version: OctoPrint 2.0.0 it is!

But with 2.0.0 it is also finally time to take care of all of the deprecated bits and pieces in OctoPrint that have been causing deprecation warnings in the logs of third party plugins for up to a decade now to go the way of the dodo. I’ve done a ton of spring cleaning the past few weeks and gotten rid of lots of left-overs that cost me plenty of maintenance overhead over the years.

What does that mean for me as a user?

For you as a user of OctoPrint who doesn’t maintain their own plugins, this might mean that once OctoPrint 2.0.0 gets fully released and you upgrade to it, some of your third party plugins will break as they have been still depending on ages long deprecated bits and pieces that I finally removed.

However, rest assured that I’m going to do what I can to keep this impact as small as possible for the community. The goal is to get in touch with affected plugin repositories right after releasing the first release candidate of OctoPrint 2.0.0, sending over pull requests to fix any incompatibilities and support authors where I can to keep things compatible.

If you want to, you can also help with this by checking your octoprint.log (you can find that under Settings > Logging) and your browser’s JavaScript console (part of your browser’s devtools) for any deprecation warnings logged by your third party plugins, and reporting those to the affected plugin’s issue tracker, quoting this blog post. If you do so, please be friendly, explain your findings, talk to the human on the other end. Don’t just post a link to this post without a comment. Help the authors of the plugins you enjoy using to get this solved 😊.

What does that mean for me as a plugin author?

If you are a plugin author, you should go through all points in this Migration Guide and check whether your plugin is affected by any of them. But please don’t get discouraged by the length of this guide. Most plugins won’t have to change anything but maybe one or two points, some not even anything at all.

To help you with identifying any issues requiring migration, Jacopo Tediosi has also published octoscanner, a small tool that allows you to automatically scan the source of your plugin for any use of deprecated bits and pieces of OctoPrint. Please note that this tool is still a very early version and false positives are possible, as well as false negatives (the tool does not yet detect all deprecations/removals, especially not frontend related things).

As a side note: If you are affected then your plugin has likely been filling octoprint.log and the browser console for years now with deprecation warnings. Nothing that’s going to be removed with OctoPrint 2.0.0 has been removed without warning. So please don’t scream at me for finally cleaning up code that’s been doing nothing but cause me maintenance overhead for the past decade 😅. And that being said, please note that there are also further deprecations announced and I’d really appreciate it if you could make sure your plugin also takes care of those now rather than right before things break 💚.

When will OctoPrint 2.0.0 be released?

I can’t say yet when OctoPrint 2.0.0 will be released as stable, but the first release candidate is quite imminent. As always, I’ll have a release candidate phase going on where the community helps testing the new version thoroughly - I cannot test all the myriad of setups you all have out there, that’s why we do it that way. Once the RCs look stable, I’ll prepare the stable OctoPrint 2.0.0 release.

Past RC phases have taken between one and two months. I expect this one to maybe take a bit longer given the heavy amount of internal changes I had to do to implement the new connector interfaces, storage support and similar.

In the end, it’ll be done when it’s done, and I’m doing the best I can to make this happen as soon as possible 😊.