Changelog includes commits released on previous minor branch already

[chillu]

Compare https://github.com/silverstripe/silverstripe-framework/blob/4/docs/en/04_Changelogs/beta/4.2.0-beta1.md with https://github.com/silverstripe/silverstripe-framework/blob/4/docs/en/04_Changelogs/4.1.2.md.

Both of them include a commit as the first item (silverstripe/silverstripe-framework@19fdebf) which was released with 4.1.2. So it shouldn't show up in the 4.2.0-beta1 changelog again. This is particularly high impact when it includes security releases, because it gives the false impression that users are getting security fixes (increasing their priority to upgrade), when they in fact might already have those security fixes in their project.

This is probably because the changelog does a diff via 4.1.0...4.2.0-beta1, rather than 4.1.<latest>...4.2.0-beta1.

[robbieaverill]

Yeah so a bug that you pointed out at the end there with not assuming the latest version correctly (how can you really assume it).

This could be fixed by #87 too, although I do agree with @tractorcow that it would add more work for the cow user. It still adds more flexibility too though.

[dhensby]

why can't cow figure out the previous release more accurately?

[tractorcow]

The bug is with the way that git log works. If you can fix the issue with git log commands you can port it to cow easily. it's not a cow specific issue.