TL;DR
The GitHub REST API has added new optional properties to various endpoints, including has_pull_requests and security_and_analysis/secret_scanning_delegated_alert_dismissal.
These changes affect multiple resources, such as /app/installations/{installation_id}/access_tokens, /events, and /orgs/{org}/actions/permissions/repositories.
The new properties are returned in the response with a 200 or 201 status code.
The changes are part of the feature updates and do not introduce any breaking changes.
Developers can expect to see these new properties in the API responses, but they are not required to take any immediate action.
What Changed
Feature: New capabilities have been added to the GitHub REST API, including the introduction of optional properties has_pull_requests and security_and_analysis/secret_scanning_delegated_alert_dismissal in various endpoints.
Who's Impacted
If you are using the GitHub REST API to fetch data from endpoints like /app/installations/{installation_id}/access_tokens or /events, you will see new optional properties in the response. If you are parsing the API responses, you may need to update your code to handle the new properties. If you are using the API to automate workflows or integrate with other tools, you should review the updated API documentation to understand the changes.
Action Checklist
☐ Review the updated API documentation for the affected endpoints.
☐ Update your code to handle the new optional properties in the API responses.
☐ Test your integrations with the updated API endpoints.
☐ Verify that your workflows are not affected by the changes.
☐ Check for any new error handling or edge cases introduced by the changes.
☐ Review the API responses for any additional properties or changes.
☐ Update your dependencies or libraries to ensure compatibility with the updated API.
☐ Monitor your application logs for any issues related to the API changes.
☐ Reach out to the GitHub support team if you have any questions or concerns about the changes.
☐ Plan for potential future changes to the API endpoints.
☐ Document the changes and updates in your internal knowledge base.
☐ Communicate the changes to your team or stakeholders.
☐ Review the API usage and adjust your implementation as needed.
☐ Test your application with different scenarios and edge cases.
Verification
The information in this update brief is based on the following sources:
[Commit 635a68eca82f](https://github.com/github/rest-api-description/commit/635a68eca82f9dbda054d26b37711d46f2de7564)
[GitHub REST API Spec Diff](https://github.com/github/rest-api-description/compare/6de8c7ee1b6379c64c5e952b6fc2c80e17f0912e...635a68eca82f9dbda054d26b37711d46f2de7564)
Last verified at: 2026-02-17T13:04:01.572304+00:00