New REST APIs for actions settings
GitHub Actions has introduced fresh REST APIs designed to handle configuration management. These new endpoints grant access to several critical settings:
- Approval requirements for fork pull request workflows initiated by external contributors
- Enabling workflows to run on fork pull requests within private repositories
- Designation of which repositories have permission to provision repository-level self-hosted runners
- Configuration of retention windows for artifacts and logs
By leveraging these endpoints, development teams can now establish, adjust, and review policies through code rather than relying on manual administrative processes. The new APIs function at three levels: enterprise-wide, organization-wide, and individual repository scope. Additional details are available in the Actions API documentation.
windows-latest image label migration
GitHub Actions will transition the windows-latest label from Windows Server 2022 to Windows Server 2025 in a phased rollout spanning September 2 through September 30, 2025. Throughout this window, workflows will incrementally move to the updated image. Following migration, workflows will exclusively run on Windows Server 2025 and will no longer execute on Windows Server 2022.
A critical consideration: Windows Server 2025 includes a different software toolkit compared to Windows Server 2022. Teams should review the Windows 2025 tool inventory ahead of time to spot any compatibility gaps and adjust workflow configurations as needed.
Additional guidance and support are available through the runner-images repository.
Source: GitHub Blog