It almost defeats the point of versioning on networked/web APIs really.
On the one hand you have library code that is semantically versioned, and for good reason those versions are immutable so if something changes you have to pull down a version. The old version is always going to work unless it's wrapping a poorly designed web API.
Web APIs are mutable, also for good reason, but it seriously hammers home the fact that whatever you build is forever and once it's out there, you can't walk it back.
The end result of that though isn't incredible API design, it usually forces your hand.
Comments
It almost defeats the point of versioning on networked/web APIs really.
On the one hand you have library code that is semantically versioned, and for good reason those versions are immutable so if something changes you have to pull down a version. The old version is always going to work unless it's wrapping a poorly designed web API.
Web APIs are mutable, also for good reason, but it seriously hammers home the fact that whatever you build is forever and once it's out there, you can't walk it back.
The end result of that though isn't incredible API design, it usually forces your hand.