Hi! Thanks for the PR! Do you have a repro for this issue? I suspect ${root_or_parent_with_any_config} might be a better setting if the issue is not finding the proper biome.jsonc file to run from.

Yes, it was noticed in this PR: freelensapp/freelens#874 You can get this commit after merge then remove settings from the .trunk.yaml and see the result: biome plugin silently ignores errors after you'll run trunk check --all -v.

If you say ${root_or_parent_with_any_config} is better then I'll switch to this option.

So it must be just ${parent} otherwise I get

          × Found a nested root configuration, but there's already a root configuration.
          
          i The other configuration was found in /private/var/folders/k5/wyp40c2n6kzfqm5_gzry576c0000gn/T/trunk-501/cMNcwD/7iasVC.
          
          i Use the migration command from the root of the project to update the configuration.
          
          $ biome migrate --write
          

        configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

          × Biome exited because the configuration resulted in errors. Please fix them.

The problem is related to biomejs/biome#6662 which was not really fixed yet and decribed in biomejs/biome#6509

Biome sees the copy of working tree in sandbox as duplicated then refuses to work.

My workaround is to use explicit --config-path option. Unfortunately, we must use explicit config file name, then it is just hardcoded to biome.jsonc as I can be just a single file in this option.

I disabled cache as a first reason of the problem that it was for long time undetected. Biome is so fast that caching is not important.