API versioning strategy for evolving systems? dont you think its a bit of a headache sometimes?

hey everyone, im thinking about the best way to handle API versioning as our system grows and changes. weve seen a few approaches like URL versioning (v1/users), header versioning (Accept: application/vnd.myapp.v1+json), or even query parameters. what are your go-to strategies for managing API versions? are there specific scenarios where one method shines over others? looking forward to hearing your experiences!