Programatic strategies for handling API deprecation

[Isaiah Schultz]

I'm wondering what sorts of strategies that folks have for staying proactive about API version deprecations that doesn't involve a human manually having to check in on the sunset dates web page every few months.

Ideally, it would be great if there was something like a RSS feed or an endpoint available within the API itself to request when a specific version of the API is being deprecated/sunset. That way, we can write some sort of build test to start flagging builds long before the sunset date when the version within the client jar gets yanked.

Is there really no good way of accomplishing that? Or am I missing something obvious?