And yet, those commits end up within the changelog file generated by the changelog plugin.
But looking closely, it is the release-notes-generator that provides the list of changes to be used.
So, I checked the release-notes-generator's code and found that it doesn't use the skip release filtration logic:
The documentation says that a commit can be excluded from the analysis by adding
[skip release]
here:And yet, those commits end up within the changelog file generated by the
changelog
plugin. But looking closely, it is therelease-notes-generator
that provides the list of changes to be used.So, I checked the
release-notes-generator
's code and found that it doesn't use theskip release
filtration logic:which is present in the core:
I see that this was added pretty long ago (3 years ago), but nothing seems to be done about it.
So, is it intentional? Or is it just some barely used feature that everybody forgot about and left the plugin outdated with inconsistent logic?