So, how do you handle API versioning when you've got a bunch of microservices?

hey everyone, im architecting a new set of microservices and we're gonna need a clear strategy for api versioning. we want to avoid breaking changes for existing clients as we evolve. what are your go-to methods? url path versioning (e.g. /v1/users), custom headers, or something else entirely? how do you manage the transition between versions, especially with multiple services interacting