Review an Actions workflow for the Node 24 migration.
Paste a sanitized GitHub.com workflow. The checker finds temporary Node 20 opt-outs, self-hosted runner review points, and action refs that need release-note or metadata inspection. It never uploads or rewrites your YAML.
Reference snapshot: July 22, 2026. GitHub began making Node 24 the default on June 16, 2026 and plans to remove Node 20 from runners later in fall 2026. The six verified action-family floors are checkout@v5, cache@v5 (including cache/restore and cache/save), download-artifact@v7, setup-node@v5, setup-python@v6, and upload-artifact@v6; dated latest-release snapshots are recorded separately. Artifact guidance is for GitHub.com. GHES has a separate upload-artifact@v3.2.2 Node 24 path, while official download-artifact guidance does not currently offer a Node 24 line.
No uploadThe checker has no network code, and the page policy blocks browser connection APIs.
No persistenceWorkflow text is not written to cookies, browser storage, or a server.
No mutationThe result is a review checklist, not an automatic dependency rewrite.
Nothing checked yet.
What the result can—and cannot—tell you.
It can triage refs
The tool parses ordinary and flow-style uses: entries, compares eight GitHub-owned refs across six action families with dated Node 24 floors and latest-release snapshots, and identifies configuration that deserves immediate review.
It cannot prove runtime compatibility
A pinned SHA hides its release line from an offline parser, third-party metadata is outside this page, and successful hosted execution depends on the actual runner, inputs, permissions, and services.
Use the migration checklist.
Map immutable SHAs to releases, review breaking changes, verify self-hosted OS and architecture, run the workflow, then remove any temporary Node 20 opt-out.
One workflow, one action-ref inventory, a reviewed minimal migration patch, runner or GHES compatibility notes, and verification evidence for $49 equivalent in Bitcoin. Scope and exact amount are confirmed in writing before payment; hosted success is not guaranteed.