Skip to content

Bump GitHub Actions to Node-24 stable versions#760

Open
LukasWallrich wants to merge 1 commit intomainfrom
ci/bump-actions-node24
Open

Bump GitHub Actions to Node-24 stable versions#760
LukasWallrich wants to merge 1 commit intomainfrom
ci/bump-actions-node24

Conversation

@LukasWallrich
Copy link
Copy Markdown
Contributor

Summary

Clears the 2026-06-02 Node 20 deprecation cutoff across all workflows by bumping every actions/* and peter-evans/* reference to its current Node-24 release.

Action From To Files
actions/checkout v4 v6 all 6 workflows (10 occurrences)
actions/setup-python v5 v6 check_images, data-processing, spell-check
actions/setup-node v4 v6 data-processing
actions/upload-artifact v4 v7 data-processing, deploy, staging-aggregate
actions/download-artifact v4 v7 deploy, staging-aggregate
peter-evans/find-comment v3 v4 check_images, spell-check
peter-evans/create-or-update-comment v4 v5 check_images, spell-check
peter-evans/create-issue-from-file v5 v6 link-check

Compatibility notes (release-notes audit)

  • All first-party actions/* v6/v7 require runner ≥ v2.327.1 — GitHub-hosted ubuntu-22.04 is well past that.
  • setup-node@v5+ added auto-package-manager caching; this repo already sets cache: 'npm' explicitly, so no behavior change.
  • upload-artifact@v7 adds opt-in archive: false direct-upload; default (zipped) behavior unchanged.
  • download-artifact@v8 would change hash-mismatch from warn → error by default. Staying on v7 preserves current behavior.
  • peter-evans/* major bumps are Node-24-runtime-only — input/output schemas unchanged.

Deliberately left alone

  • r-lib/actions/setup-pandoc@v2 — r-lib will move the v2 tag onto Node 24 before the cutoff.
  • eddelbuettel/github-actions/r2u-setup@master — composite action, no JS runtime to deprecate.
  • lycheeverse/lychee-action@v2 — major-tag pin, auto-tracks.
  • SHA-pinned peaceiris/* and dawidd6/* — deliberate security pins; GitHub's force-migration on 2026-06-02 (and the existing FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true" env var in data-processing.yml) will run them on Node 24 regardless.

Test plan

  • link-check.yaml (PR-triggered) runs on this PR — verifies actions/checkout@v6.
  • check_images.yaml (PR-triggered) runs on this PR — verifies setup-python@v6, peter-evans/find-comment@v4, peter-evans/create-or-update-comment@v5.
  • spell-check.yaml (PR-triggered) runs on this PR — same actions as above.
  • After merge, manually dispatch data-processing.yml to verify setup-node@v6, upload-artifact@v7, and end-to-end with r2u-setup + setup-pandoc@v2.
  • Watch next scheduled deploy.yaml / staging-aggregate.yaml runs to verify upload-artifact@v7download-artifact@v7 round-trip.

🤖 Generated with Claude Code

Clears the 2026-06-02 Node 20 deprecation cutoff across all workflows.

- actions/checkout v4 → v6
- actions/setup-python v5 → v6
- actions/setup-node v4 → v6
- actions/upload-artifact v4 → v7
- actions/download-artifact v4 → v7 (avoiding v8's new error-on-hash-mismatch default)
- peter-evans/find-comment v3 → v4
- peter-evans/create-or-update-comment v4 → v5
- peter-evans/create-issue-from-file v5 → v6

SHA-pinned third-party actions (peaceiris/*, dawidd6/*) and r-lib/setup-pandoc@v2
are left alone — they will be force-migrated to Node 24 by the runner.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@LukasWallrich LukasWallrich requested a review from a team as a code owner May 1, 2026 17:21
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 1, 2026

👍 All image files/references (if any) are in webp format, in line with our policy.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 1, 2026

✅ Spell Check Passed

No spelling issues found when checking 7 changed file(s)! 🎉

@LukasWallrich
Copy link
Copy Markdown
Contributor Author

LukasWallrich commented May 1, 2026

⚠️ Staging Deployment Status

This PR was attempted for staging deployment but had merge conflicts and was skipped.

Attempted at: 2026-05-08 12:30:35 UTC
Staging URL: https://staging.forrt.org

Please resolve conflicts with the base branch and the deployment will be retried automatically.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant