Feedback on this RC
Please provide general feedback on this RC in this ticket. An "All is working fine" is valuable feedback as well because it tells me people are actually testing this RC but not finding problems with it. Thanks!
Note for upgraders and plugin authors: Change in the bundling of JS assets can lead to issues in plugins
A change to solve issues with plugins bundling JS assets that cause interference with other plugins (e.g. through the declaration of "use strict") and in general to add better isolation and error handling might cause errors for some plugins that go beyond your run-off-the-mill view model and also implicitly declare new globals.
If you happen to run into any such issues, you can switch back to the old way of bundling JS assets via the newly introduced "Settings > Feature > Enable legacy plugin asset bundling" toggle (check it, save the settings, restart the server). This is provided to allow for a minimally invasive adjustment period until affected plugins have been updated.
You can find out more about the change, how to know if a plugin is even affected and what do about it on the OctoBlog.
Note for people who already ran 1.3.6rc1 and/or 1.3.6rc2, then downgraded back to 1.3.5
You'll need to do a tiny fix in your config.yaml, made necessary by a bug fixed below that was present in 1.3.6rc1 and 1.3.6rc2, or you won't be able to switch back again to Maintenance RCs to test this third RC or update to 1.3.6 stable. You'll need to remove the method: pip line under plugins.softwareupdate.checks.octoprint and then restart.
You can easily do this config.yaml change via the YamlPatcher plugin using the patch string
[["remove", "plugins.softwareupdate.checks.octoprint.method", ""]]
or via the command line using
sed -i -e "s/method: pip//g" ~/.octoprint/config.yaml
Improvements
- Fetch plugin blacklist (and also announcements, plugin notices and plugin repository) via https instead of http.
Bug fixes
- Fixed an issue causing redundant software update configuration settings to be written to
config.yaml, in turn causing issues when downgrading to <1.3.5 - Fixed an issue detecting whether the installed version is a release version or a development version.
(Commits)