Closed bkw closed 7 months ago
Found it: I needed to set include-component-in-tag: true
so previous releases would be detected.
I guess de60c24be6e93649e7192ebe2cd7078614022a40 should be mentioned in the migration guide as a non-backwards compatible change.
TL;DR
v4 does not correctly locate previous releases, wants to update from 3.12.2 to 3.0.0
Expected behavior
release and changelog should be based on previous version, v3 creates expected release 3.13.0.
Observed behavior
Both the version number and the changelog are not based on the latest release.
A possible hint as to what's going on may be the first entry in the wrongly generated changelog: the repository has been renamed at some point in the quite distant past.
Downgrading to v3 produces the correct results.
Since this is a private project, I used the following replacements in the attached logs:
myorg/my-repo previous-repo-name
Action YAML
Log output
Additional information
Repo and the module had been renamed in the past.