This second release candidate for the upcoming 1.10.0 release fixes five regressions that were reported with the first one, and also adds some improvements for newly added functionality:

✨ Features & improvements

Backup Plugin

  • Require credential recheck for download & restore.

Testing & CI

  • #4908: Also automatically publish source tarball on GitHub releases.

🐛 Bug fixes

Core

  • #4939 (regression): Fix drag’n’drop initialization.
  • #4940 (regression): Make octoprint._version backward compatible enough again to work around use on OctoPi images and third party plugins out there.
  • #4941 (regression): Fix some syntax under Python 3.7 & 3.8.
  • #4942 (regression): Fix handling of setting an empty dict on the configuration. Also added a unit test for this.
  • #4943 (regression): Fix fetching of file details for the existence check, preventing the “file already exists” dialog from making the correct checks.
  • Removed a left-over from the Access Control settings panel.

For heads-ups, highlights and fancy pictures, please see the earlier post about 1.10.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!

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.

  • User and group management functioning as expected.

  • Plugin installation functioning as expected.

  • Application key management functioning as expected. Authentication workflow with third party clients at your disposal (e.g. slicers) works as it should.

  • Backup creation, download and restore functioning as expected.

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.

Discuss!