Good morning, At the moment the Update Dependencies via Renovate step supports project selection, along with a toggle to include child projects. That is already quite useful.

One limitation, however, is that the include child projects option only scans one level deep. As a result, whenever a new repository is created in a more deeply nested structure, the step definition needs to be updated to explicitly include additional parent projects.

For example, in the following structure, enabling include child projects for Project A would still not discover Project D:

Project A/
  Project B/
  Project C/
    Project D/

To ensure all projects are covered, both Project A and Project C would need to be added to the step configuration.

A few possible improvements that could address this are:

1. Support for the same project query language that can already be used in the project overview page and API.
2. Support for the same project selection method that can be used in defining a trigger for a job.
3. The ability to parameterize project selection, allowing it to be generated dynamically during a run.
4. A configurable recursion depth for child project discovery, so users can decide how many levels deep the scan should go.

Any of these approaches would make the step easier to maintain in environments where repositories are frequently added or reorganized within nested project structures.