RAUC v1.1 Released
Just before the beautiful shine of the new has fully disappeared from RAUC 1.0, it is now time to bring out a new release: v1.1.
This release comes with some remarkable memory leakage fixes you should not miss.
As new features, we now have full support for reading GRUB2 status like we had for the other bootloader implementations already.
A minor feature but quite useful for debugging certificate issues is the new ability to use --dump-cert without requiring successful verification.
Especially system integrators may like the support for using multiple keyring certificates from a directory. This will avoid conflicts when installing multiple certificates from different build system packages.
As a result of various community feedback and discussion, this release adds a bunch of documentation updates targeting potential misunderstandings and explains some unclear topics in more detail.
We would like to say thank you to everyone who tested for v1.1, reported issues or contributed new features!
For those using A+B+recovery setups where A+B are controlled via the default boot selection logic and recovery is booted as fallback without this mechanism, RAUC also allows specifying the booted slot's name (not only the bootname) via commandline (e.g. rauc.slot=recovery.0).
Thanks to all contributors since v1.0: Angus Lees, Arnaud Rebillout, Beralt Meppelink, Enrico Jörns, Evan Edstrom, Ian Abbott, Jan Lübbe, Michael Heimpold, Rasmus Villemoes, Ulrich Ölmann, Vitaly Ogoltsov
"Getting things off the ground" could be the motto for the v1.9 release of RAUC. The support for custom metadata in the manifest got a step further, a new, more flexible, D-Bus API for bundle inspection paved the way for obtaining more detailed information, and a new manifest hash marks the first of several planned changes for configurable event logging. However, one of the most invasive changes happened under the hood: We have started the transition from autotools to meson as a build system.