I'm curious what folks' strategies are for handling the deprecation of API versions that don't involve a human having to remember to check the
sunset dates webpage every few months.
Ideally, it would be great if there was a RSS feed or some sort of endpoint in the API itself to let someone query the deprecation/sunset dates of a specific version of the API. This would allow us to implement a build-time automated check to start flagging builds when a version becomes close to its deprecation date--rather than waiting for builds to start failing on the day of sunset due to client jars no longer containing the version the app is expecting.
Is there an actual good way of accomplishing this today? I'm hoping that I'm just missing something obvious.
Thanks!