bug: changelog update fails when creating a new releasing when a pre-release with the same version is present about projen HOT 5 CLOSED

Yes please if you can! Make sure you add a test case for it.

I'm guessing the fix will be to have a more elaborate regex to match the version string?

from projen.

Looks like you are dealing with an inconsistent state here? You don't have a v0.0.1 tag yet, but already have a changelog entry for it. projen is quite likely not able to deal with these kind of inconsistency in a way that suits everyone.

What would you expect instead here? A hard error?

from projen.

Did projen somehow create changelog entry before or was it confused because I already had changelog entries for the previous beta-release tags (like v0.0.1-beta.0 and v0.0.1-beta.1)? I was thinking it was the latter because the tag strings for the beta releases like v0.0.1-beta.0 (that would be present in the changelog) contain the string v0.0.1, so it's possible that based on the check in the line I linked, projen is assuming that the changelog entry already exists.

Does that make sense or am I off-base here?

from projen.

No my bad, I think you are right. Misread the code and your comment. 🤦‍♂️

from projen.

No worries. Should I create a PR to address this?

from projen.