Dependency Inception #28993
Unanswered
kwelch
asked this question in
Request Help
Replies: 2 comments 2 replies
-
Adding a replacement for node18 to node20 might work better. Then you can specify the replacementVersion too |
Beta Was this translation helpful? Give feedback.
1 reply
-
By the way, you should update your version of Renovate. Your version was released on March 12th, that's nearly two months ago. It probably won't fix your problem, but at least you're using current stuff then. 😄 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Bitbucket
Please tell us more about your question or problem
We have a custom image wrapper around base node and java images. The image name include the major version of the language it is wrapping (ie.
golden-image-node-20
,golden-image-node-18
,golden-image-java-17
,golden-image-java-21
). These images then also follow their own version tagging.Out of the box as expected Renovate is able to manage the image tag version with no issues.
Additionally, I was able to make a custom manager that could also manage the version within the image name.
However, I am not seeing a path forward to link these into a single PR such that the image version is properly adusted based on a
node
orjava
version change.Unfortunately, the above PR from Renovate will not work, as there is no version
2.0.13
forgolden-image-node-20
.Here is the regex manager:
Out self-hosted instance is running version
37.240.1
Any help or ideas would be appreciated.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions