From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Renaming is probably not the best idea as then existing builds would no longer find the plugin and break.

You could e. g. update the description to tell to use a different plugin and also release a new version that outputs a warning that a different plugin id should be used now or something similar.

You could of course also release under both IDs, but that might confuse more than it helps.

Updating the description sounds good! And also outputting a warning would be a good idea. Do you know if it is possible to show warnings in editors like IDEA?

For the plugin itself probably not.
For the types you use to configure you could probably add deprecation annotation and IntelliJ will show it, at least for Kotlin DSL.

That's a great idea! Thank you very much!