@gaavar Thanks for picking this up!

I think there are two things to address.

Unfortunately there might be plugins importing/using ButtonBlockerAppender, so we should continue to export it. It could be deprecated. That's done by calling the deprecate function. The following will output a console warning:

import deprecated from '@wordpress/deprecated';

deprecated( 'wp.blockEditor.ButtonBlockerAppender', {
	alternative: 'wp.blockEditor.ButtonBlockAppender'
} );

The tricky bit is that the message should only be shown if the user imports ButtonBlockerAppender, so I think you'd want to wrap ButtonBlockAppender, a bit like the following code elsewhere in the codebase, and then export that as ButtonBlockerAppender 😄 :

The second thing is that there's some documentation associated with the components that needs to be regenerated (which is why the 'Static Analysis' task is failing). It can be regenerated by running npm run docs:build locally and then committing and pushing the results.