Renovate composer dependency updates doesn't respect filtering #33266
Replies: 3 comments 3 replies
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
-
Please provide a full composer.json example in a reproduction repo. If need be, the registry with filter can be a dummy address. |
Beta Was this translation helpful? Give feedback.
-
Reproduction repo created, run on our local Gitlab runner as that was easiest for me to test. You can see in the debug that "registryUrls": [
"https://version-control.it.su.org.au/api/v4/group/92/-/packages/composer",
"https://packagist.org"
], You can then seen requests like |
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.
Gitlab v19.56.3
Please tell us more about your question or problem
Composer supports filtering repositories so that you don't search a repository for dependencies that aren't there. https://getcomposer.org/doc/articles/repository-priorities.md#filtering-packages
We have a repository defined for some internal packages, but can see in the debug logs that renovate is attempting to hit API endpoints for many packages being updated. You can see in the below composer.json snippit, that only packages in the
sua/*
namespace should be searched for in the gitlab domain. But the debug logs show it searching for all packages in that repository.This doesn't prevent things from working for us, but it does mean that we are hitting the server for packages it'll never have. For some people it could break things though, is the
only/exclude
config options may be important to make sure that a dependency comes from the right repo.Logs (if relevant)
Logs
Reproduction repo https://github.com/timwsuqld/renovate-composer-filtering
Beta Was this translation helpful? Give feedback.
All reactions