I don't think that failure to write a changelog entry should be enough to
deny publishing an update to a plugin. Denying publishing of a plugin for
lack of a changelog entry seems very "heavy" to me.
It won't prevent publishing plugins when the changelog entry says "no
visible changes" or says "s
This morning I am looking at 2 more plugins that have somehow been published
without a changelog entry. Aside from this being very unprofessional, we do
not install plugin updates without changelog entries that describe what the
change is. These are almost as bad as the stupid no-user-visible-
