Composite build configuration override each other

rlatapy-luna

- [x] I have read the [guidelines for submitting issues](https://splitties.github.io/refreshVersions/contributing/submitting-issues/#bug-reports) ## 🐛 Describe the bug <!-- A clear and concise description of what the bug is. --> I know composite build is not officially supported, but: When including a project in another one by using a Gradle composite build (`includeBuild`), configuration set in `refreshVersions` block from main project `settings.gradle.kts` is overriden by configuration set in included project `settings.gradle.kts` (even if there is no configuration). ## ⚠️ Current behavior <!-- A clear and concise description of what you expected to happen. --> When running refreshVersions task, the configuration set in settings.gradle.kts is not applied ## ✅ Expected behavior <!-- A clear and concise description of what you expected to happen. --> Each projects/included projects use its own configuration without overlapping each other ## 💣 Steps to reproduce <!-- How we can reproduce the behavior: --> Here is repro project https://github.com/rlatapy-luna/CompositeRefreshVersions 1. Run `refreshVersions` task (which depends on MySubProject:refreshVersions). Both task run, but both use configuration from MySubProject (check the log and resulting `libs.versions.toml` files) 3. Run `MySubProject:refreshVersions` alone, ok <img width="1108" alt="image" src="https://github.com/user-attachments/assets/ec3d8577-1381-4ed1-af60-ea9db86d639c"> ## 📱 Tech info - [Build Scan URL](https://scans.gradle.com/s/4alr5q6cz5q46) ⚠️ It works as expected when using build `--scan`.

LouisCAD

Hello/Bonjour ! I have a plan to resolve this, but it's quite an undertaking, and since I'm the only "active" maintainer at the moment, don't expect it this year. However, if you want to contribute it in a way that I'd accept merging, I can give time to help on that so you know how to do it, where to plug things, and avoid Gradle tough tricks.