Updatesapi-github

GitHub REST API: API Changes (2026-02-05)

b896e70baa27 → 6de8c7ee1b63Verified February 17, 2026

TL;DR

  • The attestations/items/bundle response property is now nullable for the 200 status in the /orgs/{org}/attestations/{subject_digest} endpoint.
  • An optional total_count property has been added to the response of the /organizations/{org}/settings/billing/budgets endpoint with the 200 status.
  • The physical_environment request property's minimum length has been decreased from 1 to 0 in the /orgs/{org}/artifacts/metadata/deployment-record endpoint.
  • The physical_environment request property's minimum length has also been decreased from 1 to 0 in the /orgs/{org}/artifacts/metadata/deployment-record/cluster/{cluster} endpoint.
  • These changes may impact how you handle responses and requests to the affected endpoints.

    • What Changed

  • Breaking: The response property attestations/items/bundle became nullable for the 200 status in the /orgs/{org}/attestations/{subject_digest} endpoint.
  • Feature: An optional total_count property was added to the response of the /organizations/{org}/settings/billing/budgets endpoint with the 200 status.
  • Behavior: The physical_environment request property's minimum length was decreased from 1 to 0 in the /orgs/{org}/artifacts/metadata/deployment-record and /orgs/{org}/artifacts/metadata/deployment-record/cluster/{cluster} endpoints.

    • Who's Impacted

    If you are currently handling the attestations/items/bundle response property as non-nullable, you will need to update your code to account for its new nullable status. If you are using the /organizations/{org}/settings/billing/budgets endpoint, you can now utilize the optional total_count property in your responses. If you are relying on the physical_environment request property having a minimum length of 1 in the affected endpoints, you will need to adjust your requests accordingly.

    Action Checklist

  • ☐ Review the /orgs/{org}/attestations/{subject_digest} endpoint to handle the nullable attestations/items/bundle response property.
  • ☐ Update code to account for the new nullable status of attestations/items/bundle.
  • ☐ Test the /organizations/{org}/settings/billing/budgets endpoint to utilize the optional total_count property.
  • ☐ Adjust requests to the /orgs/{org}/artifacts/metadata/deployment-record endpoint to accommodate the decreased minimum length of physical_environment.
  • ☐ Adjust requests to the /orgs/{org}/artifacts/metadata/deployment-record/cluster/{cluster} endpoint to accommodate the decreased minimum length of physical_environment.
  • ☐ Verify that all affected endpoints are properly handling the changes.
  • ☐ Update documentation to reflect the changes in the endpoints.
  • ☐ Test all integrations that use the affected endpoints.
  • ☐ Review error handling for the affected endpoints.
  • ☐ Update monitoring and logging to account for the changes.
  • ☐ Communicate the changes to relevant teams and stakeholders.
  • ☐ Schedule a review of the changes after implementation.
  • ☐ Plan for potential issues that may arise from the changes.
  • ☐ Review the GitHub REST API Spec Diff for additional information on the changes.

    • Verification

    The information in this update brief is based on the following sources:

  • Commit 6de8c7ee1b63: https://github.com/github/rest-api-description/commit/6de8c7ee1b6379c64c5e952b6fc2c80e17f0912e
  • GitHub REST API Spec Diff: https://github.com/github/rest-api-description/compare/b896e70baa27bd1fd568cf5c0468554bdd9c303f...6de8c7ee1b6379c64c5e952b6fc2c80e17f0912e

    • Last verified at: 2026-02-17T13:04:11.022785+00:00

    📎 Sources