-
Notifications
You must be signed in to change notification settings - Fork 46
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
Version format check is too restrictive #263
Comments
uhafner
changed the title
Version format check is too restricitve
Version format check is too restrictive
Jan 7, 2022
Revapi parses the version strings assuming semver. |
🎉 |
Any plans for a new release? |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The version format check in RevApi seems to be too restrictive. Jenkins plugins recently moved to a CD approach which introduced version numbers that contain underscores. One example version is:
10.10.0-rc4533.47a_76fdb_150a_
. It would be helpful if RevApi can also be used with those kind of versions. Previous versions of Jenkins artifacts already contained complex versions like1.8.0-rc1165.d186b31c4c89
, but those were parsed correctly by RevApi.I also opened a bug in jenkinsci/incrementals-tools#27 but I think it might be better to have a fix here.
Exception:
Failing pull requests:
The text was updated successfully, but these errors were encountered: