You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have Gradle dependencies with shared group id and separate names, which can coincidently have the same version number.
E.g. com.group.id:first-dependency:1.1.0
and com.group.id:second-dependency:1.1.0
When the version coincidently overlap, Dependabot bumps both dependencies to the next version when only one has a new release.
Any ideas how to address this?
Tried creating groups in dependabot.yml matching the separate dependencies explicitly. But almost seems like the behaviour is to search-and-replace the version numbers only, without considering the artifact id.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have Gradle dependencies with shared group id and separate names, which can coincidently have the same version number.
E.g.
com.group.id:first-dependency:1.1.0and
com.group.id:second-dependency:1.1.0When the version coincidently overlap, Dependabot bumps both dependencies to the next version when only one has a new release.
Any ideas how to address this?
Tried creating groups in
dependabot.ymlmatching the separate dependencies explicitly. But almost seems like the behaviour is to search-and-replace the version numbers only, without considering the artifact id.It is not an issue for repositories using Gradle version catalogs.
Beta Was this translation helpful? Give feedback.
All reactions