how do you manage api versioning in a growing microservices architecture.

Hey everyone, I'm struggling a bit with API versioning now that our microservices are growing. We started with versioning in the URL path, like /v1/users and then /v2/users. It just feels kinda awkward, and honestly, it can lead to repeating code or messy routing. I've seen people do it differently, like using headers or even content negotiation. What have you guys found that actually works for handling different API versions without making things a nightmare for users and developers? What were the downsides you ran into?