Ramesh7
commented
2 months ago Thanks @smortex for reporting.
During implementation, we reviewed the change log formats for multiple modules and noticed inconsistencies across them, which has made it challenging to achieve the desired results uniformly across all modules. As a result, we are currently adhering to the change log formats generated by our supported modules i.e. gh-changelog. The observed inconsistencies are expected when the change log format is not compatible with our supported modules as a minimum viable product (MVP). We encourage other module owners to consider adopting our supported module change log format for improved visibility. Additionally, we will continue to review other change log formats as we progress and aim to onboard those that align with our objectives.
What happened?
The forge can show the relevant portion of the ChangeLog of modules which are not up-to-date:
For some organization/modules, this is not available:
Quick guess: both modules have a changelog but the format is slightly different (dash before and parenthesis around the date):
Working (generated with gh-changelog): https://github.com/puppetlabs/puppetlabs-mailalias_core/blob/main/CHANGELOG.md?plain=1
v1.2.0 - 2024-03-20
Not working (generated with github-changeLog-generator): https://github.com/voxpupuli/puppet-python/blob/master/CHANGELOG.md?plain=1
v7.3.0 (2024-02-08)
What browsers / clients are you seeing the problem on?
No response
Relevant log output
No response