New release candidate: 1.11.0rc2
This second release candidate for the upcoming 1.11.0 release fixes two regressions that were reported with the first one, as well as two bugs reported in newly added functionality:
✨ Features & improvements
Core
- Improved Tornado and CSRF failure logging.
🐛 Bug fixes
Core
- #5098 & #5100 (regression): Fixed permission fetch and
login_mechanism
setting for incoming requests with API keys. This solves the problem with all requests with an API key being responded to with an HTTP status of 403, and any API key based requests not usingGET
,HEAD
orOPTIONS
methods with a CSRF validation failure and thus an HTTP Status of 400, breaking communication with most third party clients.- #5099 (regression): Fixed templating macros being broken for third party plugins not supporting autoescaping.
Custom Control Manager
For heads-ups, highlights and fancy pictures, please see the earlier post about 1.11.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!
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 "Maintenance RCs" 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.
The newly added Custom Control Manager plugin.
The newly added Health Check plugin.
The newly added Upload Manager plugin.
The MFA-TOTP plugin using the new MFA plugin interface.
Timelapse creation, especially with a configured rendering delay.
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.
Links
- Ticket for general feedback
- Changelog and Release Notes
- FAQ entry "My OctoPrint update fails" (Read in case of any update problems!)
- How to use release channels to help test release candidate
- How to file a bug report
- Contribution Guidelines (also relevant for creating bug reports!)
- FAQ
- Documentation
- How to roll back to an earlier release (OctoPi)
- How to roll back to an earlier release (manual install)
- Published
- 03 Feb 2025
- Category
- Release
Discuss!