Utilizing another dependency to detect version number #36331
Unanswered
rwparris2
asked this question in
Request Help
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
None
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Gitlab
Please tell us more about your question or problem
My company has several applications, and an internal
company-common
library.company-common
has a bunch of common utilities and components that are used throughout out apps.company-common
has a dependency (lets call it3rd-party-ui-lib
that is a real problem child. They follow semantic-versioning loosely, patches occasionally contain breaking changes, minor releases are often breaking, and we find that ifcompany-common
andapplication-1
have different versions of3rd-pary-ui-lib
, weird shit happens.I'd like a way to configure renovate to update
company-common
normally (that is, keep3rd-party-ui-lib
up to date with it's latest release on npm. For
application-[1,2,3], I'd like renovate to use the versions defined in
company-common`, and then fallback to npm.That way, we can have renovate update
company-common
, verify it, release it, then have renovate updateapplication-1
with the new3rd-party-ui-lib
only after its been verified and released.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions