Closed robbieaverill closed 4 years ago
This could be #87 manifesting itself actually, since it's detecting the core releases as existing tags (which is true) - perhaps not picking up any changes between them.
Just another symptom of "git log is terrible for changelogs". All of these issues should be grouped together and addressed with a new changelog generator.
I think we can fix this somehow, in combination with #87
So this happens when recipes are marked as upgrade-only, e.g. silverstripe/recipe-core
. If you remove that config from cwp/cwp-recipe-cms and cwp/cwp-recipe-core for example, they are included in the changelogs.
New bug title: "upgrade only dependencies are not included in the changelog"
I've updated the description to add some more information around the expected result.
My setup:
When I generate a changelog I get (for example):
Expected result
Note the line saying
silverstripe/recipe-core from 1.1.1 to 4.2.0
- I'd expect this to include all changes in the recipe-core modules between 1.1.1 and 4.2.0 (1.2.0).This doesn't include any commits from framework, CMS etc. It's looking at the silverstripe/recipe-cms though.
Notes for the solution
PRs