how do you handle api versioning at scale?

hey folks ive been thinkin a lot about api versioning lately, esp as our services grow were movin beyond simple internal apis and startin to expose things externally, and the thought of managin diff versions without causin chaos is a bit daunting do you prefer uri versionin like /v1/users, header versionin (accept: application/vnd.company.v1+json), or somethin else entirely what are the trade-offs youve seen, esp when dealin with high traffic and complex dependencies between services