how do you handle api versioning in microservices

hey foks im wrestlin with api versining in a growing microservices archtecture weve got severl teams workin on different services and as apis evolve keepin older versins around without causin confusion or tech debt is becomin a real pain r u embeddin versin numbrs in the url v1users usin custom headers or somethin else entirely wat strategis hav worked best for u in practce especialy wen it comes to rollbacks and maintainin compatibilty