github-actions-runtime-upgrade-conventions

Upgrade the affected actions to their latest compatible stable major version, which typically moves them to a supported runtime such as a newer Node.js version. Pin each action to the release's full commit SHA and re-run the workflow to confirm the warning is gone.

Find the target release of the action, resolve it to the full commit SHA, and use that SHA in the uses field, for example actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608 with an optional version comment. Avoid mutable tags like @v4 or @main in final recommendations.

Upgrade one action at a time per commit, or one tightly related group, so failures are easy to isolate. This keeps existing workflow behavior unchanged while modernizing runtime dependencies.

Dependabot automates many action updates, but manual upgrades are still needed when Dependabot is not enabled for workflows, when runtime warnings appear before an automated update exists, or when behavior-preserving validation is required after a bump.

Confirm the edited workflows still parse with the same triggers and permissions, then run the affected workflows or equivalent local build and test commands. Check that release, signing, and artifact steps produce expected outputs and that logs show no new deprecation warnings.