The following versions were released on 22th May 2017:
- 3.1.20 ESR (changelog, upgrade documentation) – Rudder 3.1 ESR will be maintained 6 months after the 4.1 release is announced as ESR.
- 4.0.5 (changelog, upgrade documentation) – Rudder 4.0 will reach end of life the 30th June 2017. We recommend that any installations using 4.0 be upgraded to Rudder 4.1 as soon as possible.
- 4.1.2 (changelog, upgrade documentation) – Rudder 4.1 will become an ESR release, after a stabilization and observation period. It will hence be maintained at least 6 months after the following ESR release is announced.
Changelog summary
In total, 97 bugs were fixed in these releases, see the full changelog (3.1, 4.0, 4.1) for details. A few highlights are mentioned below.
These releases include the following changes:
- [#10568, 4.1] You can now adapt the behavior of Rudder when a Node is deleted with hooks
- We made a lot of changes to the documentation to improve its content, and its readability, so we hope that this new version of the documentation is much more interesting for you to use.
The following important bugs were fixed:
- [#8774, 3.1, 4.0 and 4.1] A read only user can access API tokens (which have read/write access)
- [#10734, 3.1, 4.0 and 4.1] Installation fails due to broken nss/nss-softokn detection on CentOS6
- [#9448, 3.1, 4.0 and 4.1] Missing “user techniques” in the technique editor when exporting / importing archives
- Lots of small glitches in UI fixed
- Lots of reporting bugs in techniques fixed
Upgrading
These are bug fix releases, and all installations should be upgraded when possible.
We are impatient to hear your feedback, be it comments, questions on Twitter (@RudderProject) or on IRC (#rudder on Freenode), bug reports or feature requests on the bug tracker (or of course GitHub pull requests).
As usual, follow the upgrade documentation (3.1, 4.0, 4.1) to install new releases.
