Hello again, I’m back with the second announcement of the week! There are unfortunately situations where the API needs to introduce backwards-incompatible and potentially breaking changes. For example, upgrading to TLS or dropping support for API keys. Looking forward, we see several instances where we’ll need to introduce changes like this, and decided to build a system that lets us handle them in a uniform way rather than on a case-by-case basis. We’ve published both our process around how we will roll out these changes as well as how our developers can use this system to safely migrate your apps in our deprecations documentation.
We’re first using this framework to add new security headers to our API responses. Because these headers may break some non-compliant browser clients, we’re going to give developers the opportunity to check how their apps react and make changes if necessary. You can read more about the new headers in our blog post.
Let us know if you have questions about the new security headers or the deprecations framework in general. In the very near future we’ll be using this framework to launch a major API feature so keep an eye out for that!