---
title: "GitHub Actions Node runtime upgrade: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/github-actions-node-runtime-upgrade/
description: "Nine-step upgrade of a JavaScript or TypeScript GitHub Action to a newer Node runtime, treated as a breaking major version."
---

# GitHub Actions Node runtime upgrade: review, role & definition · Undominated.ai

> Nine-step upgrade of a JavaScript or TypeScript GitHub Action to a newer Node runtime, treated as a breaking major version.

[← Explore all agents](/agents/)

CI MAINTENANCE / GitHub

# GitHub Actions Node runtime upgrade

Nine-step upgrade of a JavaScript or TypeScript GitHub Action to a newer Node runtime, treated as a breaking major version.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/github-actions-node-upgrade.agent.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 2 linked sources
 Publisher GitHub
 Licence [MIT ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/LICENSE)
 Revision 3a685010a7af
 [Read what was—and wasn’t—checked ↓](#review)

“Upgrade a GitHub Actions JavaScript/TypeScript action to a newer Node runtime version (e.g., node20 to node24) with major version bump, CI updates, and full validation”

 [GitHub · upstream description ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/github-actions-node-upgrade.agent.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - The upgrade treats a Node runtime change as a major version bump in package.json.
- The last step says to run npm run all, or the package test script, and not to claim success without a build check.

### A good fit for

 - Provide the action repository, current and target supported runner runtime, package manager and release policy.
- Receive coordinated action/package/CI/docs changes, actual build/test results and draft commit/PR text.

### Weigh up before choosing

 - Edit and terminal tools can modify the action and run project npm scripts; inspect script side effects.
- Changing runtime metadata is separate from publishing a release or moving a major-version tag.
- A parse-only fallback cannot establish runner compatibility; the mandatory major-version policy is this profile convention and needs repository agreement.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - agents/github-actions-node-upgrade.agent.md
- LICENSE
- Definition reread at the preserved revision; scoped workflow and output-contract review on 2026-10-14

### Our findings

 - Frontmatter tools are codebase, edit/editFiles, terminalCommand, and search.
- Step 1 reads action.yml runs.using and package.json before editing.
- Step 3 says a Node runtime change is a breaking change and bumps the major version.
- Step 7 says to run npm run all, or the equivalent script, and to verify the built output if no test script exists.
- It checks both runs.using and package engines, then looks for version files, bundled distribution output and native/deprecated APIs.
- Its no-test fallback is only node --check on the actual entrypoint; the definition asks for draft publication text, not automatic release/tagging.

### Not established by this review

 - The agent was not executed against a live repository or host.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/github-actions-node-upgrade.agent.md)
 - Copy the agent file at the reviewed commit into the location your host uses for custom agents.
- No install command is published. The file was not installed or run.

### Before you start

 - A GitHub Action with action.yml
- Permission for the host to edit that repository and run npm

### Compatibility

Hosts that can load a Markdown agent file · JavaScript or TypeScript GitHub Actions

### Implementation

Markdown

### Edits the action repository and can run npm

 - codebase, edit/editFiles, terminalCommand, and search.

### Cost model

MIT. The file does not state a hosted-model price.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Agent definition ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/github-actions-node-upgrade.agent.md) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/agents/github-actions-node-upgrade.agent.md Supports: summary, whySelected, permissions
- [MIT licence ↗](https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/LICENSE) Checked 2026-10-14 https://github.com/github/awesome-copilot/blob/3a685010a7afdc0dbd4c83b7fbda6c316aa516e5/LICENSE Supports: Redistribution terms

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### AWF diagnosis ↗ Fingerprints an Agentic Workflow Firewall failure, matches one finding, and reports the symptom, the finding id, and one next probe before naming a fix.](/agents/github-awf-diagnose/)[### Github Actions Expert ↗ Designs and reviews GitHub Actions workflows around minimal token permissions, immutable action references, OIDC, deployment concurrency and validation.](/agents/github-github-actions-expert/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
