3 ms·
Oh, so you’re saying that omitting the version from the header will ALWAYS return this specific version, NOT the latest version? That certainly addresses the f
by mpetrovich 4y ago
Oh, so you’re saying that omitting the version from the header will ALWAYS return this specific version, NOT the latest version?
That certainly addresses the footgun I mentioned.
EDIT: From the docs:
Requests without the X-GitHub-Api-Version header will default to use the 2022-11-28 version.
- phphphphp 4y agoYes, exactly, that’s my understanding from the blog post and changelog post. I think perhaps the waters have been muddied a little because of our expectations of API versioning + GitHub’s need to maintain backwards compatibility for existing implementations. The way I understand is that “v3” of the API (which has been around for 10 years) is now version “2022-11-28” and so existing implementations while be using version “2022-11-28” without any required change.
- saghm 4y agoI often find it useful to think of things like this as "no version specified" being the lowest version, and then explicit versions start counting after that.
- buro9 4y agoI don't see how that can be true when new versions put a 2y time bomb on old versions. At some point the default 28th Nov 2022 version is unsupported... So what is served must change... Either it's the latest at the time or the behaviour of receiving a response without providing the header is removed.