Skip to content

Bump actions/checkout off the deprecated v4 in @danielridgebot's workflows #182

Description

@ale210

Overview

We need to bump actions/checkout from v4 to v5 in all four of @danielridgebot's workflows, because v4 targets Node.js 20 and GitHub is force-running it on Node 24 on every run — when that fallback is withdrawn the workflows break, and this bot's failure mode is silence rather than an alert.

Action Items

The bot's code lives in hackforla/check-ghpages-versions — the org repo, not a personal account (the danielridgebot/check-ghpages-versions URL still resolves, but only as a redirect). The fix is one line per file, delivered as a PR on that repo.

  • Bump actions/checkout@v4 to actions/checkout@v5 in all four workflows: check-gh-pages-version.yml:13, check-ruby-version.yml:13, keepalive.yml:16, test-issue-labels.yml:11. Line numbers were accurate 2026-08-24 and may drift — find them by the uses: actions/checkout line.
  • Leave actions/github-script@v8 alone (line 44 of both check workflows). It already runs on Node 24 and produces no annotation.
  • Do not go past v5 in this pass, even though v7 is current. v5 is the pure Node 24 bump with no behaviour change. v6 moved the persisted git credential into a separate file, and three of these four workflows depend on that credential to git push a commit back to the repo. v7 additionally blocks fork checkouts for pull_request_target/workflow_run. Both are probably fine here, but neither is a one-line change any more — going current is a separate ticket that needs a real push test.
  • Run keepalive.yml on the branch via workflow_dispatch and confirm the checkout step succeeds with no Node 20 annotation. It is safe to run at any time: it prints the repo's idle age and exits 0 without committing unless the repo has been idle 50 or more days.
  • After the PR merges, confirm a scheduled run of check-gh-pages-version.yml or check-ruby-version.yml completes with no "Node.js 20 is deprecated" annotation. Both run daily (12:00 and 12:15 UTC), so this is a next-day check — it cannot be observed from the branch, because the annotation only appears on the runs that actually do the version check.

Resources/Instructions

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions