Updatesapi-github

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

0433d1ccb7b9b896e70baa27Verified February 17, 2026

TL;DR

  • The permissions/team_discussions property has been removed from multiple endpoints, including /app/installations, /app/installations/{installation_id}, and /orgs/{org}/installation.
  • New optional request properties dependabot_delegated_alert_dismissal have been added to /orgs/{org}/code-security/configurations and /orgs/{org}/code-security/configurations/{configuration_id}.
  • The /repos/{owner}/{repo}/rules/branches/{branch} endpoint has seen changes in its response properties, including the removal and addition of subschemas.
  • Multiple endpoints have had their response properties updated to remove permissions/team_discussions.
  • The changes affect various resources, including installations, applications, and code security configurations.
  • What Changed

    #### Breaking

    Changes that require immediate action include:

  • Removal of permissions/team_discussions from multiple endpoints, such as /app/installations, /app/installations/{installation_id}, /app/installations/{installation_id}/access_tokens, and /orgs/{org}/installation.
  • Updates to the /repos/{owner}/{repo}/rules/branches/{branch} endpoint, including the addition and removal of subschemas.
  • #### Deprecation

    No features are being deprecated in this update.

    #### Behavior

    Changes in existing behavior include:

  • The removal of subschemas from the /repos/{owner}/{repo}/rules/branches/{branch} endpoint's response properties.
  • #### Feature

    New capabilities added include:

  • The introduction of new optional request properties dependabot_delegated_alert_dismissal in /orgs/{org}/code-security/configurations and /orgs/{org}/code-security/configurations/{configuration_id}.
  • Who's Impacted

    If you are using the permissions/team_discussions property in your API requests, you will need to update your code to remove this property. If you are relying on the subschemas in the /repos/{owner}/{repo}/rules/branches/{branch} endpoint, you will need to adjust your code to accommodate the changes. If you are using the /orgs/{org}/code-security/configurations or /orgs/{org}/code-security/configurations/{configuration_id} endpoints, you can now utilize the new dependabot_delegated_alert_dismissal property.

    Action Checklist

  • ☐ Review API requests for usage of permissions/team_discussions property
  • ☐ Update code to remove permissions/team_discussions property from API requests
  • ☐ Test API requests to ensure compatibility with updated endpoints
  • ☐ Review usage of /repos/{owner}/{repo}/rules/branches/{branch} endpoint
  • ☐ Update code to accommodate changes to subschemas in /repos/{owner}/{repo}/rules/branches/{branch} endpoint
  • ☐ Review documentation for /orgs/{org}/code-security/configurations and /orgs/{org}/code-security/configurations/{configuration_id} endpoints
  • ☐ Update code to utilize new dependabot_delegated_alert_dismissal property
  • ☐ Test code to ensure compatibility with updated endpoints
  • ☐ Verify that all API requests are compatible with the updated endpoints
  • ☐ Review error handling to ensure compatibility with updated endpoints
  • ☐ Update testing suites to include tests for updated endpoints
  • ☐ Verify that all dependencies are up-to-date and compatible with the updated endpoints
  • ☐ Review and update any affected documentation or guides
  • ☐ Communicate changes to team members and stakeholders
  • ☐ Monitor API requests for any issues related to the updates
  • Verification

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

  • Commit b896e70baa27: https://github.com/github/rest-api-description/commit/b896e70baa27bd1fd568cf5c0468554bdd9c303f
  • GitHub REST API Spec Diff: https://github.com/github/rest-api-description/compare/0433d1ccb7b9f4353d1810156079b09a734134f7...b896e70baa27bd1fd568cf5c0468554bdd9c303f
  • Last verified at: 2026-02-17T13:04:20.305279+00:00

    📎 Sources