Timeline for How To Use Semver In REST API Versioning
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2021 at 10:07 | vote | accept | Berkin | ||
| May 6, 2021 at 5:54 | answer | added | Doc Brown | timeline score: 5 | |
| May 5, 2021 at 20:57 | comment | added | Robert Harvey | That said, have a look here. | |
| May 5, 2021 at 20:55 | comment | added | Robert Harvey | And for what it's worth, SEMVER is generally used to track software updates, not REST API changes. | |
| May 5, 2021 at 20:53 | comment | added | Robert Harvey | My impression of V numbers in URI's is that they're typically used when you create a whole new API, not to manage ordinary, breaking API changes. If you change the number of parameters, the clients are going to get a 301 or 403 anyway. | |
| May 5, 2021 at 20:52 | review | First posts | |||
| May 6, 2021 at 3:34 | |||||
| May 5, 2021 at 20:50 | comment | added | Berkin | Yeah but removing one field from request body is also breaking change, isn't it? People are going to get 403 because of this change. Can you give me an example reason of major change? Examples will help me to understand | |
| May 5, 2021 at 20:49 | comment | added | Robert Harvey |
Changing your URI from v1 to v2 is a breaking change. It's essentially a different endpoint, regardless of what happens under the hood.
|
|
| May 5, 2021 at 20:43 | history | asked | Berkin | CC BY-SA 4.0 |