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

✨ Features & improvements

Core

  • Improve JS error reporting in Firefox.
  • Fix a potential race condition that might have caused some build errors recently.

Achievements Plugin

  • Added unlocked achievements to the Anonymous Usage Tracking. Of course, this can be disabled, and if you have not opted into > tracking in the first place, nothing will be tracked, as always. Achievement stats are available on data.octoprint.org.

🐛 Bug fixes

Core

  • #4980: Fix missing temperature history for anything but the first extruder. This was actually not a > regression, but the bug only could be seen now after extending the timeline of the temperature graph to the full available history.
  • #4983 (regression): Fix prefix caching for custom defaults. Manifested in no longer being able to select > release channels in the Software Update plugin.
  • #4987 (regression): Fix creation of the static version file during installation of sdist under Windows.

Achievements Plugin

  • #4984: Make the “Mass Production” achievement detect modifications of the file.
  • Fix the “Heavy Chonker” achievement.
  • Fix the default groups for the achievement permission.

GCODE Viewer

  • #4978: Fix reloading of the same file. First thought to be a regression, turned out to not be one but was a low hanging fruit.

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!