Preleases in Python do not parse appropriately

[guzman-raphael]

First of all, thanks for making this awesome action! I've been really needing something to essentially lint and extract CHANGELOG.md details into a GH release.

That said, I did find some issues when trying to utilize this for Python pip packages. As you may or may not know, the regex for Python pip versions in PyPi is quite strict. So there are a limited number of ways that prereleases can be defined. Specifically, when we define a version as 0.1.0a1, the parsing fails along with the prerelease designation. Did some debugging myself and determined that the only issue is that the hyphen (-) is strictly enforced for prereleases.

I have a version that works for our needs on my fork but unsure how it will affect other use-cases. I'll soon issue a PR so that we can discuss any unwanted impact to see if we can determine a good way to handle all cases including Python prereleases.

[mindsers]

Hello, thanks for taking the time to open this issue (and the related PR). It is much appreciated.

This is an interesting case that I still don't know how to solve right now. I mean, this action pretend to work with projet following SEMVER rules and as far as I understand your link, the public version identifier of Pip project doesn't follow the SEMVER rules.

Right now, we use the REGEX provided by the SEMVER project to detect version numbers.

I'm wondering what is the best way to handle this:

• modifying the REGEX (as you did) but it won't strictly detect and verify SEMVER version number anymore.
• add support for other format
• allow custom format
• something else..

[mindsers]

Also, I just thought that it could break the linting part of the action because it needs to understand (for each format supported: currently only SEMVER) how major/minor/fixes/prerelease/etc are defined to be able to apply the correct linting rules.

We can update the part too if needed. That's not the problem. But we definitely have to take it into consideration too when deciding if (and how) we want to support other format or not.