What version?

differs

Which command?

proto install

What happened?

With newer versions of proto the old config schemas are not valid anymore and proto will complain about an unknown setting and will abort operation.

Like settings.default-registry (I know it was hidden, but worked perfectly in older moon versions!) and now with the plugins.backend settings.

It would be great if not known settings would be ignored on starting proto commands.

Ignored can also be

(1) Warn user, but keep the setting if there will be a need of downgrading proto
(2) Warn user, remove these settings

My prefered solution would be (1)...

Because some old installations already modified the ~/.proto/.prototools, and now jumping to a newer version of proto will bring the errors.

Trace logs?

No response

Operating system?

Linux

Architecture?

x64