This is similar to the versioning scheme used by AWS and it worked well there. V... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

bilalq on Nov 29, 2022 | parent | context | favorite | on: Enabling the Future of GitHub's REST API with API ...

This is similar to the versioning scheme used by AWS and it worked well there. Versioning was rarely done, but this was a clean scheme for surfacing breaking changes to users. https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-...

It is a little surprising that the version defaults to the 2022-11-28 rather than defaulting to latest if omitted, but I guess that's a way to err on the side of not breaking old users when they upgrade an SDK.

timrogers on Nov 29, 2022 [–]

Author here. You've hit the nail on the head on why we default to 2022-11-28 - it's all about protecting the hundreds of thousands of of existing GitHub integrations that rely on our current behavior.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact