Deprecation of beta GitHub Copilot usage API endpoint

Summary

Beginning February 2025, the beta Copilot /usage endpoints will be deprecated.
No new data will be inserted for retrieval via the beta /usage endpoints. This endpoint will be accessible through February, but the 28 day retention policy will remain.

Who’s impacted?

Enterprise organizations with Copilot licenses not yet migrated from the /usage metrics APIs are impacted by this deprecation.

What’s changing and why?

The deprecation of the beta /usage endpoints is a part of GitHub’s effort to deliver more powerful and flexible data offerings for enterprises, organizations, and teams. The new endpoints provide:
– Visibility into the adoption and consumption of Copilot across various stages of dev lifecycle (from code suggestions to PR reviews), from the team to the enterprise level
– Expanded scope of metrics, with the addition of GitHub.com Copilot Chat and Copilot for Pull Requests
– Consistent terminology with the user management API
– Better visibility into unique users at various drilldowns

Next steps

Ensure your organization is no longer consuming the now deprecated /usage endpoints in any jobs, workflows, and analytics tools.
As an alternative to the beta Copilot /usage endpoints, check out the PowerBI template and the Copilot /metrics endpoints.

Join the discussion in the GitHub community.

Edit the GitHub-owned image on a larger hosted runner

Starting today, customers can change the runner image on larger hosted runners without deleting and re-creating them. You can now update the image and the change will be applied on all future workflow runs to that label. For customers using static IPs, you can change the image on your runner while keeping your IP addresses the same.

Note: partner images cannot be edited at this time and still require the runner to be deleted and re-created.

To edit your runners, follow the steps outlined in our documentation.

See more

Copilot Autofix is available for more code scanning alerts

Copilot Autofix helps you fix code scanning alerts and avoid introducing new security vulnerabilities by using large language models to suggest potential fixes.

We recently expanded the range of CodeQL security alerts where Copilot can suggest an autofix, covering a group that accounts for 29% of all CodeQL alerts. This expansion led to an 8% overall increase in alerts with an available autofix and a 270% increase in autofixes for this specific group of improved alerts. With more autofix suggestions, you can resolve security issues identified by CodeQL more easily—either by applying Copilot’s suggested fix directly or using it as a starting point for your own edits.

We made these improvements by analyzing our usage data to understand the most common types of alerts where Copilot was not suggesting fixes and then made a targeted effort to improve autofix for these alerts. Read more about the testing process that GitHub uses to identify the quality of autofix suggestions.

We continuously evaluate the performance of CodeQL and Copilot Autofix, so look for more improvements in the future.

See more
View all changes