Support releases with multiple changelogs

[dobladov]

Added

• Support releases with multiple changelogs

[gotbahn]

Just to be sure we are targeting the same, I was thinking about next

1. Determinate release branch
2. Check modified project/package folders, can come as input or recursively check which ones containing changelogs
3. If folder contains changes, then start checking changelog
   3.1. Last changelog entry has version and date
   3.2 Last changelog version matches one in sibling package.json & -lock
   3.3. Target branch changelog version !== last entry one

[gotbahn]

no guarantee it's true

[dobladov]

But we are talking about release branch, in this case at least one must be modified.
And it case is not the correct one it should fail in the rest of the checks.

[nitzanashi]

Let's say I didn't modified the Changelog of SEO but I created a release Branch and PR to production, it might be that other changelogs are modified (e.g. App, embed) so It won't fail because there are changelogs that are being updated but these are not the one that we interested in.

[dobladov]

This check only happens when only 1 changelog is modified, in this example you are modifying more than one, so it won't go to this check.

But lest's say that we had only 1 previous modified changelog, you could trigger this check only if you did not modify at all the changelog for SEO, but why make a release branch if you don't make any change?

[nitzanashi]

Isn't that why we have The changelog action? to validate this?

[dobladov]

@z-merge it