rangeStrategy of pin requires current version to exist on a registry since 37.194.4 #28981
Unanswered
duckmatt
asked this question in
Request Help
Replies: 1 comment
-
Please make a minimal reproduction with readme. Your test one is not minimal:
I assume only a single dependency is necessary to reproduce this? |
Beta Was this translation helpful? Give feedback.
0 replies
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 think I found a bug
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.
No response
Please tell us more about your question or problem
Hello,
When we have a
rangeStrategy
ofpin
and have a current version that doesn't exist, we end up withinvalid-value
as the currentVersion and this results in no MR/PR being created.I believe this behaviour changed since: #27383
I have a minimal example here: https://github.com/duckmatt/renovate-test/
In the action https://github.com/duckmatt/renovate-test/actions/runs/9033730289/job/24824695087 it runs the same code against both renovate versions:
37.194.3
:37.194.4
:In my real scenario the version that doesn't exist is a snapshot on a snapshot specific maven registry, however there are thousands of versions per dep, currently this results in thousands of HTTP calls to check the pom exists when we make the registry available. We are able to get around this by enabling
RENOVATE_EXPERIMENTAL_NO_MAVEN_POM_CHECK
& adding the snapshot registry or using therangeStrategy
ofreplace
.Is there any chance of allowing pin to fall through to https://github.com/renovatebot/renovate/blob/main/lib/workers/repository/process/lookup/current.ts#L52-L54 or were we relying previously on a bug?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions