This is not so simple. The suggestion was to don't warn about dependencies included in the "never" list.

Sorry, I misunderstood what he meant. I will try to modify the code logic according to your explanation.

Now the problem with this change is that if someone will add the neverBuiltDependencies field while there is no onlyBuiltDependencies field, all the dependencies will be automatically allowed to be built.

I'll make onlyBuiltDependencies an empty array even if neverBuiltDependencies is set.

But with that change it becomes impossible to allow all dependencies to be built. Which some users might want to get the pre v10 behaviour. Maybe we could allow to disable the behaviour by setting onlyBuiltDependencies to false.

Maybe it would be better to create a new field for excluding dependencies from the warning. Something like ignoredBuiltDependencies.

Can we make these configurations global? Configuring each project separately in a project with multiple packages can be troublesome. refer #8891 (comment)

Responded #8891 (comment)