Expired GitHub Actions artifacts no longer shown in UI and API
Expired artifacts are no longer displayed in the GitHub Actions run summary or returned by the REST API. Previously, expired artifacts remained visible with an "Expired" pill indicator.
Expired artifacts are no longer displayed in the GitHub Actions run summary or returned by the REST API. Previously, an expired artifact remained visible with an “Expired” pill, even though the underlying files had already been deleted from storage.
That leftover pill left some users unsure whether they were still being billed for storing artifacts that no longer existed. To remove that ambiguity, expired artifacts will not be shown when viewing run data, including:
- The list of artifacts on a workflow run summary page.
- The list artifacts for a repository and get an artifact REST API endpoints.
If you need to know which artifacts a workflow run produced after they’ve expired, you can still find that information in the run’s logs. This change doesn’t affect artifact retention settings or billing—it only changes how expired artifacts are displayed.
The post Expired GitHub Actions artifacts no longer shown in UI and API appeared first on The GitHub Blog.
Source: original entry ↗
More from GitHub
Follow GitHub to get its new changes in your feed and email digest.
Copilot model policy API for enterprise, orgs, and teams
REST API endpoints now available to retrieve and update Copilot model policies for enterprises, teams, apps, and organizations, enabling centralized policy management at scale.
GitHub Copilot models deprecated
GitHub has deprecated certain models across GitHub Copilot experiences including Chat, inline edits, and code completions, effective October 19, 2026. Users may need to migrate to supported models.
Some Git over HTTPS may temporarily require authentication
GitHub may temporarily require authentication for clones and fetches of public repositories over HTTPS during periods of unusual traffic to protect service availability.