how do u handle schema evolution in ur microservices tho

We've been having some trouble with schema changes in our microservices. The thing is, different services update at different speeds. So, sometimes a schema change in one service causes problems for another service that hasn't updated its code yet to match. Have you guys run into this? What have you found that works for handling it? Are you guys doing versioned APIs, contract testing, or a completely different approach?