Module Spotlight: Changelogify! Now with Drupal security advisory coverage
A while back I posted here about a contrib module I was building called Changelogify.
Someone commented that they liked the idea and would try it once it had security coverage.
Well, it finally does :)
Changelogify now has a stable release covered by Drupal’s security advisory policy.
For anyone who missed the original post, Changelogify automatically captures changes happening on a Drupal site and lets you group them into human readable releases. Things like content changes, module operations, and user changes can become an editable release that you publish as a changelog.
The idea is to bridge the gap between raw logs and the release notes we usually end up writing manually.
Since I first posted it here, I’ve also done quite a bit of work on the module as part of getting it production ready, including:
Drupal 10 and 11 support
expanded event tracking
configuration hardening
better release generation
a draft and review workflow
a themeable public /changelog page
automated testing and CI
Drupal security advisory coverage
Going through the security review process was honestly pretty useful in itself. Reviewers caught things around Drupal conventions, hooks, compatibility, project structure, routing, and testing that made the module better.
So, to the person who said they’d try it when it got security coverage: your move 😄
And seriously, if anyone here uses it on a real Drupal project, I’d love feedback. Especially bugs, missing events you think it should capture, or ways the workflow could fit better into how agencies and Drupal teams handle releases.
Changelogify: Drupal.org/project/changelogify
Install with Composer:
composer require 'drupal/changelogify:^1.2'