github-actions-2025

Modernize GitHub Actions workflows for 2025 runner, security, and platform changes.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/moughamir/justwaitit-review --skill github-actions-2025-moughamir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-2025
Source: https://github.com/moughamir/justwaitit-review/tree/main/.agents/skills/github-actions-2025
Command: npx skills add https://github.com/moughamir/justwaitit-review --skill github-actions-2025-moughamir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of GitHub Actions pipeline breakage and rising CI costs by showing how to adopt 2025 platform changes—runners, artifact handling, release immutability, and security/governance updates—so automation remains reliable and efficient.

Core Features & Use Cases

  • 1 vCPU Linux Runners (Public Preview): Use lower-cost, short-timeout runners for lightweight automation like issue triage, label management, PR comments, and simple Git operations.
  • Immutable Releases (August 2025): Create releases that cannot have assets or tags changed or deleted to improve supply-chain security and auditability.
  • Node24 Migration (September 2025): Update workflows to use Node24-compatible action versions and runner support ahead of Node20 deprecation.
  • Security & Governance Improvements: Apply allowed-actions policy updates with explicit blocking and SHA pinning, and require approval for Copilot-triggered workflows.
  • Workflow Maintenance Updates: Migrate artifacts to the February 2025 architecture, retire windows-2019 runners by moving to windows-2022/windows-latest, and use environments for protected deployments.

Quick Start

Update your workflows to use ubuntu-latest-1-core for short automation jobs, switch to SHA-pinned action references, migrate any deprecated artifact upload steps to actions/upload-artifact@v4+, and set production deployments to use a protected environment named production.

Frequently Asked Questions about github-actions-2025

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate GitHub Actions workflows to Node24 before deprecation?

To migrate GitHub Actions workflows to Node24, update setup steps to use Node24-compatible action versions and ensure runner support is updated ahead of the September 2025 Node20 deprecation deadline.

What are immutable GitHub releases and how do I enforce them?

Immutable GitHub releases prevent assets or tags from being changed or deleted. Enforce immutable releases by using GitHub release creation APIs and flags to improve supply-chain security and auditability.

Can I use GitHub Actions 1 vCPU runners for CI automation?

You can use 1 vCPU Linux runners for lightweight GitHub Actions CI automation like issue triage and label management. These lower-cost runners have short timeouts, making them unsuitable for heavy tasks.

How do I pin GitHub Actions versions to SHAs for security?

Pin GitHub Actions versions to SHAs by updating workflow references to use commit SHAs instead of version tags. This security governance improvement allows explicit blocking via allowed-actions policies.

How do I migrate artifact uploads to the GitHub Actions 2025 architecture?

Migrate artifact uploads to the 2025 GitHub Actions architecture by updating deprecated artifact upload steps to use actions/upload-artifact@v4 or higher to ensure platform compatibility and reliability.

When should I not use GitHub Actions 1 vCPU runners?

You should not use GitHub Actions 1 vCPU runners for heavy deployments or long-running tasks. They are designed for lightweight automation with short timeouts, so use standard runners for complex CI jobs.