-
Notifications
You must be signed in to change notification settings - Fork 470
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
Spock's versioning confuses Dependabot #1697
Comments
Dependabot is just one of the many fields this makes problems. I also always disliked this encoding in the version. I still think the proper solution would be to leverage feature variants for this. |
I had similar issue with Renovate and there it was possible to add some extra rules as a workaround:
Maybe something similar is also possible with Dependabot? |
Got the same problem today, nothing else comes in mind but ignoring Spock in dependabot ;( |
Describe the bug
Due to the versioning scheme of Spock 2.x having the Groovy compatibility encoded in the version, Dependabot will always send updates to the groovy-4 variant.
To Reproduce
org.spockframework:spock-core:2.1-groovy-3.0
gradle
as thepackage-ecosystem
org.spockframework:spock-core:2.3-groovy-4.0
(or whatever the latest 2.x release is at that time)Expected behavior
Spockframework should use the classifier portion of the GAV to indicate Groovy compatibility. That way Dependabot can distinguish between the two Groovy variants.
Actual behavior
Spockframework appends the variant information to the version number, which isn't recognized by Dependabot.
Java version
N/A
Buildtool version
N/A
What operating system are you using
Mac
Dependencies
org.spockframework:spock-core:2.1-groovy-3.0
Additional context
No response
The text was updated successfully, but these errors were encountered: