I upgraded to Discourse 3.5.0.beta6-dev (da0b303568) this morning.
After the update I was met with a red banner across the top of the site saying:
Admin notice: you’re using the discourse-add-groups-to-about theme component. This feature is now available in Discourse core. You should remove this theme component.
No, but I haven’t installed the component. Maybe that’s why the migration didn’t happen for me. But I wasn’t really interested because I don’t use the feature.
In fact, I follow the PRs on GitHub mainly because the screenshots help with translation, especially for features like this that are not available in the interface at first.
It’s in core, but the show_additional_about_groups setting is still a hidden site setting, so it’s not visible.
I think the migration enabled it for sites which used the component before. I am not sure if it will be enabled for everyone or simply be removed. I think it is only needed during the migration process.
If I have understood correctly, the idea is that the show_additional_about_groups setting is added to core. Then a check is added to the theme component so that the groups are only displayed if show_additional_about_groups is false. This means that it simply continues to work as before. Afterwards everything is built in core, but only displayed if show_additional_about_groups is true.
After the settings have been automatically migrated, show_additional_about_groups is activated. Now the code from core shows the groups and no longer the component.
This migration was added 3 days ago. Then 2 days ago the notice was added in the component that was displayed to you.
I don’t know why the migration obviously didn’t work for you (neither the settings were automatically applied, nor was show_additional_about_groups activated).
I think it is definitely an oversight that the global warning does not check whether the user is an admin.