api versioning strategies, which one do you prefer

Hey everyone, I've been wrestling with API versioning lately. We've got a few options like URI versioning (v1, v2), header versioning (Accept header), and even query parameters. Each seems to have its own pros and cons regarding discoverability, caching, and client adoption. What approach do you find yourselves reaching for most often in production, and what are the main reasons behind that choice? Curious to hear about your experiences and any pitfalls to avoid.