BOMnipotent Version 0.4.0 has breaking changes
It overhauls logging, and fixes several usability and one small security issue.
What, another release?
Developing with a completely test-driven approach is really paying off. Sure, it slowed me down at the beginning, but now that I have the infrastructure in place, I can introduce five changes into BOMnipotent within a few days.
The product is in its beta phase, or young adulthood, if you allow the anthropomorphism. Breaking changes can and do still happen.
The biggest one is an overhaul of the logging behvaiour of the client. I want to make it consistent and easy to use and understand early on, instead of piling up technical debt and justifying it with the infamous phrase “historically grown”.
The other two changes stretch the definition of “breaking”: A seldomly required parameter in the CSAF upload has now become optional, and user accounts do now need to exist before they can be assigned any role.
As always, a full changelog is found in the doc pages.
Speaking of, this release is accompanied by a new batch of documentation pages. You can now find a detailed description of how to manage access to your BOMnipotent data by setting up users, roles and permissions. This is the last doc release that comes in a batch, because I now consider the doc pages mature. Just like BOMnipotent, they will probably never stop growing, but every important aspect of the program is now described with examples.
I hope you enjoy using the new version as much as I enjoy creating it!