Four billings endpoints have suddenly disappeared from the GitHub v3 API

[gmlewis]

When updating openapi_operations.yaml, I discovered that four billing-related endpoints have suddenly disappeared from both the OpenAPI metadata and the official GitHub v3 API documentation website:

• GET /orgs/{org}/settings/billing/packages
• GET /orgs/{org}/settings/billing/shared-storage
• GET /users/{username}/settings/billing/packages
• GET /users/{username}/settings/billing/shared-storage

Without live testing on an org with billing, it will not be clear whether these endpoint still actually exist or not.

As a stop-gap measure, I will keep the endpoints around but remove them from the automated openapi tools.

[Not-Dhananjay-Mishra]

I found this Announcement related to it

[gmlewis]

I found this Announcement related to it

Thank you, @Not-Dhananjay-Mishra!

Now the question becomes: How long do we keep these endpoints in the repo for Enterprise users before removing them, since many are invariably running on older versions of the platform?

[Not-Dhananjay-Mishra]

Now the question becomes: How long do we keep these endpoints in the repo for Enterprise users before removing them, since many are invariably running on older versions of the platform?

Out of curiosity, why can’t we remove them now? If the endpoints are retired and also removed from GitHub API Docs, I believe there won’t be any response returned.

[gmlewis]

Now the question becomes: How long do we keep these endpoints in the repo for Enterprise users before removing them, since many are invariably running on older versions of the platform?

Out of curiosity, why can’t we remove them now? If the endpoints are retired and also removed from GitHub API Docs, I believe there won’t be any response returned.

So we have this challenge of needing to support GitHub Enterprise customers who invariably have older versions of the GitHub server running on-premises, and therefore are not up-to-date with the latest version of the public GitHub server.

If you search the issues in this repo for "enterprise" support, you will find a large amount of requests, including discussions on how to best support them and NOT removing deprecated fields, etc. It's a bit of a challenge.

[elminster-aom]

... and NOT removing deprecated fields, etc.

Agree, but in my opinion, we should mark them as depreciated in the code at least.