redhat-cop / redhat-cop/openshift-virtualization-migration-documentation
fix: upgrade Node.js from EOL v18 to v22 in publish workflow
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Problem
.github/workflows/publish-github-pages.yml pins node-version: '18'. Node.js 18 reached End-of-Life in April 2025 and no longer receives security patches. GitHub Actions hosted runners will eventually deprecate it, and using an EOL runtime is a security and stability risk.
# current
- name: Install Node.js
uses: actions/setup-node@v4
with:
node-version: '18'
Proposed Solution
Upgrade to Node.js 22 (current Active LTS). Antora and its dependencies are fully compatible with Node 22.
# fix
- name: Install Node.js
uses: actions/setup-node@v4
with:
node-version: '22'
Files to Change
.github/workflows/publish-github-pages.yml
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open .github/workflows/publish-github-pages.yml and inspect the Install Node.js step. Change the pinned runtime from Node.js 18 to 22, then verify the workflow uses node-version: '22' and that no other file needs updating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 92/100