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

ERROR Missing section for previous release in CHANGELOG.md with no increment option #29

Open
WirthAware opened this issue Oct 13, 2022 · 3 comments

Comments

@WirthAware
Copy link

We updated recently to the latest release-it version and keep-it-changelog version.
We have an release job in our CI todo automated Gitlab release with release-it but after the update we got an error.

We are using an internal company release versioning, so we use release it with the --no-increment version
and use the version from our package.json instead. Verything was working with those versions:

"@release-it/keep-a-changelog": "2.3.0",
"release-it": "14.12.1",

With the latest version we got the following Error

ERROR Missing section for previous release ("12.0.0") in CHANGELOG.md.

In our package.json the version is version": "12.0.0 in that example.

So we have an Unreleased section in our changelog and the last versions in our changelog.
But it seems keep a changelog thought there should be a last version 12.0.0 but it is the current version that needs to be released.

We had a look into the code on github and tried to debug this. And its working with increment option. When when setting the --no-increment its not working.
Looking into the code we found some conditions and i guess it seems there is a bug. Also what we noticed in the config object lastVersion is given with isIncrement option but with no increment option last version is not passed into config object.
Maybe you could have a look into it ?
We reverted the update but would be great to be able to update and use latest features.

Cheers

@yusuf963
Copy link

@WirthAware , have you found any fix for that? I got the same error msg

@yusuf963
Copy link

@WirthAware , it seems that the fix for this error is to add "strictLatest": false, to the @release-it/keep-a-changelog plugin object

@webpro
Copy link
Contributor

webpro commented Feb 15, 2024

A bit late to the party, but is the issue resolved with @yusuf963's suggestion, @WirthAware?

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

No branches or pull requests

3 participants