CHANGELOG incompatibility with GPM #16
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello @finanalyst,
I have noticed in our GPM logs that your plugin's CHANGELOG is not compatible with GPM. Our GPM is quite sensible to the way the CHANGELOG is structured and it does require consistency. This PR should fix the problem for you and I also wanted to highlight what type of changes I have made for you to know in the future.
new,bugfixandimprovedas sections of a changelog. Would be great to support some of the ones you came up with such as documentation, minor, change but at this time we do not support those.Also, don't group multiple entires of the section name. Only 1
[](#bugfix)per version should be present.12/23/2020for EU today's format would be23-12-2020. I have updated all your dates to reflect that.Also, the date is quite important to be just a date, the format
< 28 April 2018is not supported. I did set that date for you to31-01-2018which appears to be your very first commit on the repository.# v1.0.0 - v1.2.0), CHANGELOGs are supposed to be the journal of each singular version. Particularly in Grav we have a feature that allows to display the CHANGELOG of a resource from the current version installed to the latest available. This would not work if the version definition was in range format.