HTTP Header Field for URI Obsolescence / Expiration

I am creating a REST service where I want to implement a way to discount certain URIs when they should no longer be supported for one reason or another. As functions are deprecated, they will be replaced by new ones that work in similar (but not the same) ways. This means that at some point I will have to start answering 410 Gone.

The idea is that all client software should be updated, and, say, six months later, all users should be updated. At this time, outdated URIs will begin to tell the client that it is outdated so that the client can display a message to the user. This time is not known in advance and cannot be explicitly recorded in the documentation.

The problem I want to solve is this:

Is there an HTTP header field that I should use to indicate that a particular URI will stop working at a specific time, and if so, which one?

This is not the first time anyone wants to solve this problem. Is there an unofficial header field that is already in use, or should I create my own? Please note that I do not want to add this information to the content itself, as this means that each resource has been changed and needs to be updated by the client, which, of course, is not the case.