Rudder 4.0.6 and 4.1.3 released

The following versions were released on 23th May 2017:

  • 4.0.6 (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.3 (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, 3 bugs were fixed in these releases, see the full changelog (4.0, 4.1) for details. A few highlights are mentioned below.

We made this release due to a bug in rudder-agent packages, preventing it from sending an inventory right after the installation (would only be generated during inventory time (00:00 am – 06:00 am) and when triggered manually via rudder agent inventory).

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 (4.0, 4.1) to install new releases.

Share this post

Scroll to Top
Rudder robot

Directive NIS2: how to get ready? Rudder can help you

Security management module details

This module targets maximum security and compliance for managing your infrastructure, with enterprise-class features such as:
Learn more about this module on the Security management page

Configuration & patch management module details

This module targets maximum performance and reliability for managing your infrastructure and patches, with enterprise-class features such as:

Learn more about this module on the Configuration & patch management page