CHANGELOG and release inconsistency

[mkbreuningIOHK]

Is this a regression?

No

Description

Looking at https://github.com/input-output-hk/atala-prism-wallet-sdk-swift/blob/main/CHANGELOG.md, it shows up to the version v4.0.0.

When selecting the tag, you can see that there have been subsequent versions: 5.0.0, 5.0.1, 5.0.2. But they are not showing consistent info:
https://github.com/input-output-hk/atala-prism-wallet-sdk-swift/blob/5.0.2/CHANGELOG.md: it does show 5.0.2 and 4.0.0 but not 5.0.1 and 5.0.0
https://github.com/input-output-hk/atala-prism-wallet-sdk-swift/blob/5.0.1/CHANGELOG.md: it does not show 5.0.1 info but only 4.0.0.
https://github.com/input-output-hk/atala-prism-wallet-sdk-swift/blob/5.0.0/CHANGELOG.md: it does show 5.0.0 and 4.0.0

And when checking the releases: https://github.com/input-output-hk/atala-prism-wallet-sdk-swift/releases, it shows 5.0.2, 5.0.0 and 4.0.0, but 5.0.1 is not showed.

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in

No response

Anything else?

No response

[mkbreuningIOHK]

@goncalo-frade-iohk , additional observation with release v6.0.0: not sure if it is to be checked or not:
CHANGELOG.md observations

• changelog on main branch will show only up to v4.0.0 but not the other releases that came after: v6.0.0, v5.0.2, v5.0.0.
• changelog on v6.0.0 tag: will show v6.0.0 and v4.0.0 only and the delta is only showing the commit feat(demo): update demo app with new features #133 while the release is showing 5 more differences compared to previous release v5.0.2 (which is correct).
• If I look at the commits history, the list should be the ones from v5.0.2 to v6.0.0 ()

COMMITS observations

• List of commits on main: the commits are shown but there is no chore(release) info since the release v4.0.0.
• If you go to the list of commits under tag v6.0.0, you will see the commits from v4.0.0 to v6.0.0, but the chore(release) v5.0.0 and v5.0.2 are not shown.

RELEASES observations

• Note that the release v5.0.0 is shown prior to v4.0.0 while its date is after (27-Feb vs 4-Feb respectively).
• According to the list of commits under tag v5.0.2, the previous release is v4.0.0, which is not correct as it should be fix: schema download optional #116 , ci: change for release branches #117 , docs: jazzy broke so now we will use docc #118, ci: add codeowners #119, feat!: move to swift based framework for didcomm, jose and peer did #120, test: add e2e pipeline + html report #121, docs: update the PR template #122, fix: update apollo that has an important fix for app publishing #128. But the release note is just showing: fix: update apollo that has an important fix for app publishing #128

[mkbreuningIOHK]

@essbante-io , adding stale label without a comment is not giving direction: this issue was not considered since it was submitted, only by me a second time to give additional information.
The triage should tell if the information I have provided is good enough to reproduce or not the issue.

• If good enough, then the priority is decided.
• If not good enough, some information are asked.

[amagyar-iohk]

@yshyn-iohk I believe we can close this one. The problem was caused by the branches we were using to release and semantic-release wasn't able to pickup other versions from other branches, therefore not generating the full log. We are switched back to have the releases from main.

[yshyn-iohk]

Let's discuss this with @goncalo-frade-iohk

[yshyn-iohk]

I don't know if we perform the release of all SDKs from the main branch.
There is a special process to release SDK-TS from the release branch, as far as I remember.

[yshyn-iohk]

assigned to @goncalo-frade-iohk to make a decision and added to the backlog column.