Changelog.MD is not properly created

[lordrip]

Describe the Bug

When cutting a release, the generated Changelog is not correct, as it always brings the v0.2.0 version again.

Steps to Reproduce the Bug or Issue

1. Dispatch "Create a Pull request for a new release" workflow

2. Notice how the generated pull request includes again the v0.2.0 version

Screenshots or Videos

No response

Platform

• OS: [e.g. macOS, Windows, Linux]
• Browser: [e.g. Chrome, Safari, Firefox]
• Version: [e.g. 0.30.0]

[apupier]

it is because the tag was created outside of the main branch:

[apupier]

there will be the same issue with the next release as the v0.4.0 is also outside of the main branch:

[apupier]

as an example, the v0.4.0 should have been created on the 7d4ece4 commit

[lordrip]

In that case, if I delete the releases and create the tag again, it should be ok?

[apupier]

tags are now created on the main branch so the changelog is correctly created

[lordrip]

@apupier this issue refers to the chagelog.md file not being properly created, I think the issue remains because the last time this changelog was modified was 10 months ago

[apupier]

ah my bad, I thought it was related to the changelog attached to the tags, for instance https://github.com/KaotoIO/kaoto/releases/tag/2.2.0

[lordrip]

That one is good, because... we do it by hand :shushing_face:

[apupier]

I click on "generate changelog" and after only sorting by hand the list of bullet points. Which is now possible because the first problem discovered when investigating on this issue is fixed (the tag to be on the main branch)

So means we will not more investigation to know what is the current problem for the changelog.md files. I usually prefer to create them by hand to have a better readbaility on my othe rprojects so not famailair ith custom tooling used to generate it :-(