Skip to content
Permalink
Browse files

Preparing release of 1.2.17

  • Loading branch information...
foosel committed Nov 8, 2016
1 parent 2f79d9d commit 6976ac9edd45770fe258811cf41ffe701b07dfc7
Showing with 17 additions and 33 deletions.
  1. +15 −32 CHANGELOG.md
  2. +2 −1 SUPPORTERS.md
@@ -1,43 +1,15 @@
# OctoPrint Changelog

## 1.2.17rc4 (2016-10-17)

### Bug fixes

* Properly handle empty JS file list from plugins. Solves a 500 on OctoPrint instances without any third party plugins installed generated during web asset bundling introduced in 1.2.17rc2.

([Commits](https://github.com/foosel/OctoPrint/compare/1.2.17rc3...1.2.17rc4))

## 1.2.17rc3 (2016-10-13)

### Bug fixes

* Fixed a wrong order in loading JS files on the client introduced in 1.2.17rc2 to make the UI more resilient against broken plugin JS.

([Commits](https://github.com/foosel/OctoPrint/compare/1.2.17rc2...1.2.17rc3))

## 1.2.17rc2 (2016-10-13)

### Improvements

* Improved the `serial.log` logging handler to roll over serial log on new connections to the printer instead of continuously appending to the same file. Please note that `serial.log` is a debugging tool only and should *not* be left enabled unless you are trying to troubleshoot something in your printer communication.
* Split JS/CSS/LESS asset bundles according into asset bundles for core + bundled plugins ("packed_core.{js|css|less}") and third party plugins ("packed_plugins.{js|css|less}"). That will allow the core UI to still function properly even if an installed third party plugin produces invalid JS and therefore causes a parser error for the whole plugin JS file. See [#1544](https://github.com/foosel/OctoPrint/issues/1544) for an example of such a situation.

### Bug fixes

* Fixed a bug causing the update of OctoPrint to not work under certain circumstances: If 1.2.16 was installed and the settings were *never* saved via the "Settings" dialog's "Save", the update of OctoPrint would fail due to a `KeyError` in the updater. Reason is a renamed property, properly switched to when saving the settings.
* Fixed the logging subsystem to not properly clean up after itself.

([Commits](https://github.com/foosel/OctoPrint/compare/1.2.17rc1...1.2.17rc2))

## 1.2.17rc1 (2016-10-06)
## 1.2.17 (2016-11-08)

### Improvements

* Files like `config.yaml` etc will now persist their permissions, with a lower and upper permission bounds for sanitization (e.g. removing executable flags on configuration files but keeping group read/write permissions if found).
* Log full stack trace on socket connection errors when debug logging for `octoprint.server.util.sockjs` is enabled
* ``SettingsPlugin``s may now mark configuration paths as restricted so that they are not returned on the REST API
* Updated LESS.js version
* Improved the `serial.log` logging handler to roll over serial log on new connections to the printer instead of continuously appending to the same file. Please note that `serial.log` is a debugging tool only and should *not* be left enabled unless you are trying to troubleshoot something in your printer communication.
* Split JS/CSS/LESS asset bundles according into asset bundles for core + bundled plugins ("packed_core.{js|css|less}") and third party plugins ("packed_plugins.{js|css|less}"). That will allow the core UI to still function properly even if an installed third party plugin produces invalid JS and therefore causes a parser error for the whole plugin JS file. See [#1544](https://github.com/foosel/OctoPrint/issues/1544) for an example of such a situation.

### Bug fixes

@@ -46,8 +18,19 @@
* Fixed issue causing ``remember_me`` cookie not to be deleted properly on logout
* Fixed broken filter toggling on ``ItemListHelper`` class used for various lists throughout the web interface
* Fixed an issue with the preliminary page never reporting that the server is now up if the page generated during preliminary caching had no cache headers set (e.g. because it contained the first run setup wizard)
* Fixed a bug causing the update of OctoPrint to not work under certain circumstances: If 1.2.16 was installed and the settings were *never* saved via the "Settings" dialog's "Save", the update of OctoPrint would fail due to a `KeyError` in the updater. Reason is a renamed property, properly switched to when saving the settings.
* Fixed the logging subsystem to properly clean up after itself.
* Fixed a wrong order in loading JS files on the client introduced in 1.2.17rc2 to make the UI more resilient against broken plugin JS.
* Properly handle empty JS file list from plugins. Solves a 500 on OctoPrint instances without any third party plugins installed generated during web asset bundling introduced in 1.2.17rc2.

([Commits](https://github.com/foosel/OctoPrint/compare/1.2.16...1.2.17rc1))
### More information

* [Commits](https://github.com/foosel/OctoPrint/compare/1.2.16...1.2.17)
* Release Candidates:
* [1.2.17rc1](https://github.com/foosel/OctoPrint/releases/tag/1.2.17rc1)
* [1.2.17rc2](https://github.com/foosel/OctoPrint/releases/tag/1.2.17rc2)
* [1.2.17rc3](https://github.com/foosel/OctoPrint/releases/tag/1.2.17rc3)
* [1.2.17rc4](https://github.com/foosel/OctoPrint/releases/tag/1.2.17rc4)

## 1.2.16 (2016-09-23)

@@ -59,6 +59,7 @@ thanks to everyone who contributed!
* Peter Grace
* Peter Schmehl
* PRINT3Dforum.com
* Robert Gusek
* Roger Strolz
* Roy Cortes
* Samer Najia
@@ -73,4 +74,4 @@ thanks to everyone who contributed!
* Thomas Hatley
* Trent Shumay

and 933 more wonderful people pledging on the [Patreon campaign](https://patreon.com/foosel)!
and 968 more wonderful people pledging on the [Patreon campaign](https://patreon.com/foosel)!

0 comments on commit 6976ac9

Please sign in to comment.
You can’t perform that action at this time.