Skip to content

fix: Update Node.js to v20 in publish and retract workflows#6964

Merged
BYK merged 1 commit into
mainfrom
fix/update-node-version-in-workflows
Jan 21, 2026
Merged

fix: Update Node.js to v20 in publish and retract workflows#6964
BYK merged 1 commit into
mainfrom
fix/update-node-version-in-workflows

Conversation

@BYK

@BYK BYK commented Jan 21, 2026

Copy link
Copy Markdown
Member

Summary

Fixes the publish workflow failure caused by PR #6953.

The recent dependency updates require Node.js >= 18 (@octokit/core@5.2.2 specifically), but the workflows were still using Node.js 14, causing yarn install to fail with:

error @octokit/core@5.2.2: The engine "node" is incompatible with this module. Expected version ">= 18". Got "14.21.3"

Changes

  • Update node-version from 14 to 24 in publish.yml, retract.yml, and test.yml
  • Update actions/checkout from v3 to v6
  • Update actions/setup-node from v3 to v6
  • Replace manual actions/cache with setup-node's built-in yarn cache in test.yml

@BYK BYK requested a review from a team as a code owner January 21, 2026 13:28
@BYK BYK force-pushed the fix/update-node-version-in-workflows branch 2 times, most recently from 273837d to 7d70e12 Compare January 21, 2026 13:34
The recent dependency updates require Node.js >= 18. The publish
workflow was failing because it was still using Node.js 14.

Changes:
- Update node-version from 14 to 24 in all workflows
- Update actions/checkout from v3 to v6
- Update actions/setup-node from v3 to v6
- Update actions/cache from v3 to v4
- Simplify cache key in test.yml (only yarn.lock needed)
@BYK BYK force-pushed the fix/update-node-version-in-workflows branch from 7d70e12 to f8d6b55 Compare January 21, 2026 13:35
@BYK BYK merged commit 2d287a9 into main Jan 21, 2026
8 checks passed
@BYK BYK deleted the fix/update-node-version-in-workflows branch January 21, 2026 13:38
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