How to update pinned versions for local>
presets?
#37723
Unanswered
josiblair
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.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
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
Summary
On a self-hosted Renovate connected to a self-hosted GitLab, my downstream repos pin a shared preset using the
local>
prefix.I see in the docs that Local Presets are unsupported for the
renovate-config-presets
automatic dependency updates, so I’m looking for guidance on a supported way to auto-bump a pinnedlocal>
preset on self-hosted GitLab.Goal
0.10.6
,1.0.0
, …).Example Config Extending Preset
What happens
Renovate recognizes the preset but lists it as unsupported for updates:
So the
#0.10.6
never bumps, even though newer tags exist in the preset repo.What I've Tried
Switching
local>
togitlab>
Using:
On our self-hosted GitLab, Renovate did not use our self-hosted endpoint; it behaved as if
gitlab>
referred togitlab.com
, so resolution failed.If there’s a config to map
gitlab>
to a custom base URL on self-hosted, apologies as I couldn't find where it was in the docs.Custom regex manager to bump the
#
tag insideextends
I tried parsing the
currentValue
and sourcing versions viagitlab-tags
to update thelocal>
line. Renovate appears to preventcustomManagers
from modifying files/sections handled by the renovate-config-presets
manager, so no update occurred.Tagging verified
The preset repo is semver-tagged (
0.10.6
,1.0.0
, …), and the file exists at those tags.What I expected
Either:
A way for
gitlab>
preset references to resolve against a self-hosted GitLab base URL so the presets manager can auto-bump pinned#tags
, orA supported approach to auto-update pinned
local>
presets (e.g., a mapping fromlocal>
→{gitlab-tags, registryUrl}
), orThe ability for a
customManager
to update theextends
tag whenrenovate-config-presets
declines to.Question
Could this be related to the preset file naming docs note about deprecating renovate.json as the default preset file name and recommending default.json?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions