ACTIONS RUNTIME DEPRECATION CHECK · RUNS IN YOUR BROWSER

Which of your workflow steps run on a deprecated Node runtime?

GitHub warns “Node.js 16 actions are deprecated” one run at a time. Paste your workflow YAML below and this page lists every actions/* step pinned to a major that runs on an end-of-life Node runtime, or that GitHub has shut down, with the file, the line and the major to move to.

Nothing is uploaded. The YAML you paste is read in this browser and never leaves your device, and this tool makes no network calls of its own.

1. Paste one or more workflow files

Copy the contents of each file under .github/workflows/ you want checked. Add more blocks for more files — nothing here reads your repository, so pasting is how it sees anything.

Paste at least one workflow file above and click Check.

Prefer a CLI, or want this in your own CI?

Same logic, zero dependencies, one file:

python3 check.py                  # scan .github/workflows under the current directory
python3 check.py /path/to/repo    # scan a specific checkout
python3 check.py --format json    # machine-readable
python3 check.py --fail-on-risk   # exit 2 on shut-down / deprecated findings

Get check.py from the repo — stdlib only, nothing to install, no network calls. Wire --fail-on-risk into your own CI to block an end-of-life action version before it merges; Node 20 notices stay informational.

Common questions

What does the “Node.js 16 actions are deprecated” warning mean?

GitHub runs JavaScript actions on a Node runtime chosen by each action’s major version. When that runtime reaches end of life, GitHub annotates every run that uses the old major and later forces a newer runtime, which can change behaviour. This tool lists every step that triggers it, with file and line.

Which actions have been shut down entirely?

actions/upload-artifact and actions/download-artifact v1 to v3, and actions/cache v1 and v2, are no longer served by GitHub, so jobs using them fail rather than warn.

Is Node 20 a problem today?

Not today. It is reported as informational because GitHub has announced moving the runner default to Node 24. It never counts as a risk.

Does this tool cover third-party actions or SHA-pinned refs?

No. It covers a short list of first-party actions/* actions. A commit SHA or a branch such as @main cannot be mapped to a major version, so those lines are skipped, not judged.

Does this tool send my workflow anywhere?

No. It makes no network calls. Paste your workflow YAML and the scan runs entirely in this page.

Does a clean scan mean my workflows are up to date?

No. The version-to-runtime table is a labelled snapshot (as of 2026-10) and covers only some actions. Confirm against each action’s action.yml (runs.using) and release notes before upgrading.