-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
CR versions should be recognized as release candidates #673
Comments
GeorgEchterling
pushed a commit
to GeorgEchterling/refreshVersions
that referenced
this issue
Mar 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Describe the bug
Hibernate uses CR as their marker for release candidates. RefreshVersions only recognizes
RC
asStabilityLevel.ReleaseCandidate
. Because of this, the following configuration does not filter out Hibernate's release candidates as expected:Versions such as
6.2.0.CR1
and6.2.0.CR2
are recognized asStabilityLevel.Stable
.✅ Expected behavior
Versions such as
6.2.0.CR1
and6.2.0.CR2
should be recognized asStabilityLevel.ReleaseCandidate
.💣 Steps to reproduce
6.1.X
line.rejectVersionIf
.6.2.0.CR1
and6.2.0.CR2
.The text was updated successfully, but these errors were encountered: