What are the current best practices for API versioning?
DRF seems to support it, but it requires to have a “switch” per version. If we support SemVer, every minor version would lead to a new serializer!
I’m sure there must be a better way. Do you guys know? 
I’m not seeing what the problem or issue is. Can you explain why you think this is true?
I don’t see why you couldn’t assign the same serializer to multiple versions.
Hi,
I suggest you to take a look on this blog and the playlist mentioned in the blog.
https://www.meritedin.com/blogs/api-versioning
This may answer your question.
Regards,
Sowthri S
Hi,
Please refer the below blog. You may have an idea on API Versioning.
https://www.meritedin.com/robust-api.html
Please don’t forget to take a look on the videos listed on their playlist.