GitHub Actions Unifies Run and Check Retention to 90-Day Policy

GitHub announced that starting October 1, 2026, GitHub Actions will unify its lifecycle governance by subjecting checks, workflow runs, and commit statuses to the existing artifact and log retention policy. Previously, workflow run execution records, check results, and commit statuses persisted for over 400 days regardless of custom log eviction settings. Under the new policy, the configuration is consolidated under a single control—renamed in the management console to "Check, workflow run, status, artifact and log retention"—defaulting to 90 days, with public repositories hard-capped at 90 days and private organizations bound by their enterprise ceilings. For DevOps engineers, platform administrators, and FinOps practitioners, this policy shift fundamentally alters how long CI/CD execution lineage remains queryable directly via GitHub APIs and the web interface. Unifying retention solves two common platform headaches: it purges millions of stale execution records that slow down dashboard loading and API responsiveness, and it automatically sheds orphaned storage costs for artifacts tied to stale runs. However, for organizations in regulated environments—such as healthcare, finance, or defense—losing check metadata after 90 days without an automated external archiving pipeline can trigger serious compliance violations during annual audits. This update reflects a broader industry movement across major DevOps and cloud platforms toward aggressive metadata lifecycle management and resource hygiene. As developer teams have shifted to continuous deployment and high-frequency pull request workflows, CI/CD platforms generate massive volumes of ephemeral data daily. Retaining unstructured telemetry, transient check runs, and run-status mappings indefinitely is unsustainable for platform performance. Like recent policy changes across cloud registries and observability systems, GitHub is prioritizing core platform execution speed and deterministic storage governance over native, indefinite log archival. Practitioners must audit their organization-wide retention policies before the October 1 cutoff. First, teams that depend on GitHub Actions API data to generate compliance attestations, release metrics, or DORA dashboards must immediately export workflow run metrics to external time-series databases or security information and event management (SIEM) systems. Second, administrators should evaluate whether adjusting the unified retention duration upwards is worth the trade-off, as extending the window will also prolong artifact and log retention, potentially inflating billable Actions storage. Finally, teams should remember that this change is non-retroactive; once data is purged under the 90-day threshold, it cannot be recovered by extending retention settings later.