Nope, for some reason I guess my brain thought this was not a PR on the discourse org
Will merge shortly after the CI checks run.
I did that. But I still have the impression that it helps only for forums adding the component after I changed this. On those already using it, the new default isn’t applied (which is usually good!). So I still see the problem that there is an unexpected change in behavior for those already using the component.
Also do you know what happens if an admin configured a setting with a group which I add as a disallowed group in my update?
For cases like these and others in future, I think the best way is probably writing a migration on a per theme/component basis Migrate Discourse theme settings