Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CHANGELOG and release inconsistency #131

Open
mkbreuningIOHK opened this issue Mar 28, 2024 · 2 comments
Open

CHANGELOG and release inconsistency #131

mkbreuningIOHK opened this issue Mar 28, 2024 · 2 comments
Labels

Comments

@mkbreuningIOHK
Copy link
Contributor

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
Copy link
Contributor Author

mkbreuningIOHK commented May 6, 2024

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

COMMITS observations

RELEASES observations

@mkbreuningIOHK
Copy link
Contributor Author

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants