GitHub Actions
5 articles in the last 30 days.
-
Red Hat Enterprise Linux runner images now generally available
RHEL 9 and RHEL 10 images for GitHub-hosted larger runners have reached general availability. Existing preview runners keep working unchanged, and the images are available on Team and Enterprise Cloud plans.
-
De-fanging dangerous triggers in GitHub Actions across an organization
GitHub will block the pull_request_target trigger by default in public repositories from December 2, 2026. The PSF removed risky triggers across its GitHub organizations and documented how to roll out the policy.
-
Hackers Found a Way Around GitHub SHA Pinning. This Webinar Explains How to Close the Gap
Attackers bypassed SHA pinning of GitHub Actions by planting malicious code in the Trivy scanner in March 2026. The piece promotes a webinar on closing the gap.
-
Build, Test and Release Extensions with the New PGXN GitHub Actions
David Wheeler presents three new GitHub Actions that replace the Docker-based pgxn-tools: a release action for PGXN, a matrix action for Postgres versions, and a Postgres server action.
-
Lock your GitHub Actions
GitHub Actions now supports workflow lockfiles via the gh-actions-lock extension, so workflows can use readable version tags while commit SHAs are pinned. Renovate and Dependabot already update them.