Bug: globalExtends
no longer works for repositories
and autodiscovery
with v38
#32307
Replies: 2 comments 3 replies
-
After experimenting with Is this known behavior, a bug, or did we misconfigure or misunderstand some of the configuraoitn options? |
Beta Was this translation helpful? Give feedback.
-
This was resolved in release 40.3.3 |
Beta Was this translation helpful? Give feedback.
-
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.
Bitbucket Server
Please tell us more about your question or problem
We have the following setup:
We have a central configuration we reuse in multiple environments.
The selection which repositories should be processed we extracted into a separat config which is imported with
globalExtends
.With v37 this worked quite well. With the update to v38 this stopped working completely. According to the release notes, there is a change with
globalExtends
but I think we should be unaffected by it. The change switched the precedence so that the globalExtends has lower priority, but we have the configuration only in one place.A little bit more concrete. We have this renovate configuration:
The
globalExtends
fileonboarded-repositories.json5
looks like this:With this configuration, no repository will be processed.
We tried to do it with autodiscovery, and add just the filters to the
onboarded-repositories.json5
file, with the result that all repositories are processed, like the content of theglobalExtends
is ignored.Could this be a regression or where are we going awry?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions