Unsupported range strategy when using custom manager with ruby versioning #28090
Replies: 3 comments 12 replies
-
What is the request here - to support rangeStrategy=pin for custom managers? |
Beta Was this translation helpful? Give feedback.
-
Hi there, Please do not unnecessarily For example, never It's OK to comment in an issue or discussion after multiple days or weeks. But please, still don't Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
-
Resolved by #33800 |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I think I found a bug
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
37.265.0
Please tell us more about your question or problem
We were using
regexManagers
as a workaround to support version updates in.gemspec
files. After upgrading tocustomManagers
we now see the following warning in the dependency dashboard:The renovate config in question:
An an example repository can be found in mpkorstanje/renovate-gemspec-minimal-example. Ideally I would be able to set the
rangeStrategy
on the custom manager, or lacking one, fall back to the gobaly configured range strategy.Note: This issue is spun out from #10616.
Debugging notes
While debugging 37.265.0 against the example it appears that this code here:
renovate/lib/modules/manager/index.ts
Lines 79 to 83 in 3bfad40
Is checking against the
managerList
which do not include thecustomManagers
rather than theallManagersList
:renovate/lib/modules/manager/index.ts
Lines 16 to 19 in 3bfad40
And then
null
returned bygetRangeStrategy
eventually ends up ingetNewValue
renovate/lib/modules/versioning/ruby/index.ts
Lines 143 to 144 in 3bfad40
Now technically what the correct resolution would be I'm not sure. The
customManagers
appear to be a list of strings rather than actual manager objects.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions