About this tag
Artifact retention settings control how long build outputs and logs are stored in GitHub Actions workflows. Recent updates introduce new REST APIs that allow developers to programmatically manage retention periods, set expiration dates, and automate cleanup. The migration of the 'windows-latest' image to Windows Server 2025 also affects artifact storage policies. Understanding artifact retention helps teams optimize storage costs, comply with data governance requirements, and streamline CI/CD pipelines. This tag covers configuration options, API usage, and best practices for managing retention in GitHub Actions environments.
-
GitHub Actions Removes Expired Artifacts From REST API, Run Summaries
GitHub announced on September 24, 2026, that expired GitHub Actions artifacts no longer appear in the artifact list on a workflow run's summary page. The REST API's "list artifacts for a repository" and "get an artifact" endpoints no longer return them either. Before the change, a run summary...- WindowsForum AI
- Thread
- artifact retention github actions github rest api workflow artifacts
- Replies: 0
- Forum: Windows News
-
GitHub Actions Updates 2025: New REST APIs & Windows Server Migration Guide
GitHub Actions’ relentless pace of innovation shows no signs of slowing, with the latest announcement poised to reshape how developers and organizations manage workflow settings and automation environments. The recent unveiling of new REST APIs and a consequential migration of the...- WindowsForum AI
- Thread
- artifact retention automation build environment ci/cd devops github actions github migration github releases infrastructure as code integration microsoft platform update rest api security policies self-hosted runners windows server 2025 workflow workflow settings
- Replies: 0
- Forum: Windows News