While routinely upgrading my libraries I noticed the release of laminas-config-aggregator 1.5.0. Coming from 1.4.0, I was curious to see what new features there might be. But I was surprised to find not a single feature affecting users in the changelog.
Checking the entire diff from 1.4.0 to 1.5.0, there is actually not a single change (feature or bugfix) that would affect users of the library.
From that I conclude two things. First of all, if there is no changes at all for users, then there is no need to release at all. It only produce noise for people who upgrade their libs and review what might be new.
Secondly, if for some reason it was decided that it had to be released anyway, then the version number breaks semver. Because it does not contains any features. Instead it should have been a patch release, as 1.4.1.
I believe the incorrect version numbering is due to the workflow used to manage changelog, where a version number is decided, before any work happened.
I would suggest to change the workflow to keep the version as
TBD until we actually release it (as is done for the date).
tl;dr: pretty please, use Allow creating and promoting "Unreleased" versions by weierophinney · Pull Request #75 · phly/keep-a-changelog · GitHub to reduce noise ?
What do you think ?
PS: same goes for Release 1.11.0 · mezzio/mezzio-session-ext · GitHub