luceos I think it's up to the site map author to ignore private posts as this is a flag in core and byobu simply interacts with it
I know, and in this regard I was a little slopyy. So this is more a question of updating your extensions and adjusting them to changes in the core. So the responsibility is with the sitemap extension that didn't adapt to such a change. But I guess, there are other scenarios thinkable, where the responsibilities are less clear.
you can already mark which extensions conflict with yours using composer.
That's good, I didn't think of that. How will this conflict be communicated to a potential user of an extension?
This only works if you know about it though.
So we come back to a chart that lists all tested combinations. And if you want to use a combination that is not approved yet, you at least know that you get into untested waters.
