GitHub retention now deletes checks, workflow runs and statuses

Historical workflow and check records now follow existing Actions retention settings. Public repositories can keep them for no more than 90 days.

Historical workflow and check records now follow existing Actions retention settings. Public repositories can keep them for no more than 90 days.
GitHub says checks, workflow runs and statuses on github.com now disappear automatically once they exceed the configured GitHub Actions retention period—the limit on how long records are kept. The expanded policy took effect on October 1, 2026.
The same setting already governed artifacts, or saved workflow files, and logs. It now also governs records of workflow executions and their checks and reported statuses. The rule covers checks and statuses created by third-party applications as well as GitHub Actions.
In its August 27 advance announcement, GitHub said checks, workflow runs and statuses had previously remained available for more than 400 days, regardless of retention settings. They now follow the configured Actions period, which defaults to 90 days. Teams reviewing old workflow activity can therefore lose access to records sooner than under the previous policy.
GitHub’s stated reason for expanding the policy is to reduce stale data stored across Actions, helping keep checks, workflow runs and statuses fast and reliable.
A repository can increase its retention period only within the caps set by its organization and enterprise. Public repositories have a maximum of 90 days for checks, workflow runs and statuses, matching the existing limit for artifacts and logs. The setting is labeled “Check, workflow run, status, artifact and log retention” in the interface.
Keeping records longer can also affect costs because the shared setting keeps artifacts and logs longer. GitHub says those files and logs count toward billable Actions storage, while metadata—the descriptive records—for checks, workflow runs and statuses does not.
Changing the setting does not restore records already deleted under a retention policy, just as it does not restore deleted artifacts or logs. GitHub advises teams to review their retention window and export or archive anything they need to keep beyond it.

Engadget’s warning concerns an existing image-upload default, not a new try-on policy. Its corrected report also says Instant Checkout has been discontinued.
2 min

The open-source tool’s 100% coverage measures instruction recognition, not broad game compatibility. Dreaming Sarah remains the only game the project lists as verified playable on PC.
4 min

The reported fabrication targeting Bianca Motley Broom shows how verification can lag behind circulation. Georgia’s proposed deepfake protections remain unenacted, though existing defamation law offers a possible remedy.
2 min