gitlabci does not resolve into trigger-included gitlab-ci versions #16652
pritho
started this conversation in
Suggest an Idea
Replies: 3 comments 1 reply
-
This is currently simply not supported by renovate, so it's not a bug. Please open a discussion in future, so we can decide if it's by design / a feature request or a bug. |
Beta Was this translation helpful? Give feedback.
0 replies
-
seems to be supported meanwhile, can be closed |
Beta Was this translation helpful? Give feedback.
0 replies
-
@pritho @viceice Was support for this ever added? #16819 seems to resolve it, but in my own tests it doesn't seem to work as expected? |
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
-
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us what version of Renovate you run.
v32.119.1
Please select which platform you are using if self-hosting.
GitLab self-hosted
If you're self-hosting Renovate, tell us what version of the platform you run.
15.1.2
Was this something which used to work for you, and then stopped?
I never saw this working
Describe the bug
trigger-included gitlab-ci templates are not correctly resolved and managed.
Only the main include is being properly resolved.
In this example, only v0.0.1 would be updated, but not v0.1.0 to an existing later release.
Minimal reproduction repo: https://gitlab.com/thopr/renovate-gitlab-ci
Included repo (tags v0.0.1, v0.1.0 & v0.2.0) : https://gitlab.com/thopr/ci-template
Relevant debug logs
Logs
Have you created a minimal reproduction repository?
I have linked to a minimal reproduction repository in the bug description
Beta Was this translation helpful? Give feedback.
All reactions