Writing a test to prevent method signature changes

When building an SDK it is best practice not to change method signatures so you don't break any clients (including name and parameters). How can I write a unit test or unit tests to make sure people don't change the method signatures of my Java SDK when contributing to it?