4 ms·
I also found it odd that they switched from URL versioning to an HTTP header. Sure if I’m writing an integration that’s no big deal, but it makes it more of a
by chrismeller 4y ago
I also found it odd that they switched from URL versioning to an HTTP header.
Sure if I’m writing an integration that’s no big deal, but it makes it more of a PITA to do things from the CLI with curl.
- datapolitical 4y agoWell, you don’t need the header
- chrismeller 4y agoYou don’t need it if you’re expecting the current 2022-11-28 version, but it seems like you’ll need it to “opt-in” to any future ones, which presumably includes new endpoints that don’t even exist in the current.
- timrogers 4y agoAuthor here. We consider new endpoints to be non-breaking changes, so they’ll be available in 2022-11-28.
- chrismeller 4y agoAh, ok. Well personally that seems even worse. Adding new things to the existing “version” just seems crazy.
- akoncius 4y agodepends on how you define "version" here. seems that github took "version changes when backwards compatibility is broken" version which can mean that you can deploy 20 new features but if those are new then "version" does not change. that would be my guess
- deleted 4y ago[deleted]