-
Notifications
You must be signed in to change notification settings - Fork 471
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
Semver package check did not work with alpine packages #920
Comments
Hello, thank you for filing this. https://stackblitz.com/edit/node-semver-check-ocyv5l?file=index.js Type |
basically yes. the r0 is a release suffix not a prerelease. So the bug is in the semver lib right? |
The way I'm reading the semver spec, the behavior of the node and go libraries seem accurate. My guess is alpine doesn't strictly follow semver for their package versions. https://semver.org/#spec-item-2 |
The explanation of Alpine versioning. It follows not strictly semver: https://wiki.alpinelinux.org/wiki/Package_policies#Package_versions |
Right, goss doesn't support Alpine (or any other package format) versioning currently. The only one supported is semver. |
A little bit related to: |
I'll create a new feature request for Goss to support version comparison for all supported package managers: alpine, rpm, deb, etc. I'll close this ticket and #334 when I create the new comprehensive feature request. This has been a gap in Goss for a long time now and should be addressed.. I think since I last looked at it, there may be more libraries that handle version comparisons of the different package types. Hopefully there's mature libraries for all, otherwise, Goss may have to implement some from hopefully well defined specs. |
There is a similar issue with an implementation: google/osv-scanner#952 under Apache2 license. |
Describe the bug
Semver versions check for package doesn't work with alpine packages. The actual package version for curl is
8.5.0-r0
How To Reproduce
>=8.4.0
is green. it seams that-r0
is interpreted as release candidateExpected Behavior
valid
Actual Behavior
error
Environment:
The text was updated successfully, but these errors were encountered: