Preparing release of 1.3.6rc3

This commit is contained in:
Gina Häußge 2017-12-07 17:40:04 +01:00
parent 133a4658ee
commit 17e6f5d508
2 changed files with 13 additions and 17 deletions

View file

@ -1,15 +1,19 @@
# OctoPrint Changelog
## 1.3.6rc3 (2017-12-08)
### 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
([Commits](https://github.com/foosel/OctoPrint/compare/1.3.6rc2...1.3.6rc3))
## 1.3.6rc2 (2017-12-05)
### 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](http://octoprint.org/blog/2017/12/01/heads-up-plugin-authors/).
### Bug fixes
* [#2262](https://github.com/foosel/OctoPrint/issues/2262) - Fixed a bug causing `Error:checksum mismatch, Last Line: ...` errors from the firmware to be handled incorrectly.
@ -21,14 +25,6 @@ You can find out more about the change, how to know if a plugin is even affected
## 1.3.6rc1 (2017-12-01)
### 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](http://octoprint.org/blog/2017/12/01/heads-up-plugin-authors/).
### Improvements
* [#203](https://github.com/foosel/OctoPrint/issues/203) - Allow selecting the current tab via URL hashs. Also update URL hash when switching tabs, thus adding this to the browser history and allowing quicker back and forth navigation through the browser's back and forward buttons.

View file

@ -59,4 +59,4 @@ thanks to everyone who contributed!
* Timeshell.ca
* Trent Shumay
and 1144 more wonderful people pledging on the [Patreon campaign](https://patreon.com/foosel)!
and 1143 more wonderful people pledging on the [Patreon campaign](https://patreon.com/foosel)!