Skip to content

ci: update to Node.js 26 and current GitHub Actions - #7246

Open
aetherloop wants to merge 1 commit into
yarnpkg:masterfrom
aetherloop:ci/update-node26-and-actions
Open

aetherloop wants to merge 1 commit into
yarnpkg:masterfrom
aetherloop:ci/update-node26-and-actions

Conversation

@aetherloop

Copy link
Copy Markdown

What's the problem this PR addresses?

CI runs on Node.js 25, which reached end-of-life on 2026-06-01, and the workflows pin GitHub Actions (actions/checkout@v4, actions/setup-node@v4, actions/cache@v4, etc.) that run on the deprecated node20 runtime. GitHub now force-runs them on newer Node and emits deprecation annotations.

Closes #7235

How did you fix it?

  • Bumped the default Node.js used by CI from 25.6 to 26.x in the prepare composite action.
  • Updated the GitHub Actions to their current major versions: checkout v4→v7, setup-node v4→v7, cache v4→v6, upload-artifact v4→v7, download-artifact v4→v8, github-script v6→v9, stale v6→v11.

The minimum supported Node.js (18.x) and the integration test matrix are intentionally left unchanged.

Checklist

  • I have read the Contributing Guide.
  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

Node.js 25 reached end-of-life on 2026-06-01, and the pinned GitHub
Actions (checkout/setup-node/cache on node20) are deprecated on GitHub
runners.

- Bump the default Node.js used by CI from 25.6 to 26.x in the prepare
  composite action.
- Update actions to their current major versions:
  checkout v4->v7, setup-node v4->v7, cache v4->v6,
  upload-artifact v4->v7, download-artifact v4->v8,
  github-script v6->v9, stale v6->v11.

The minimum supported Node.js (18.x) and the integration test matrix
are left unchanged.

Closes yarnpkg#7235
@aetherloop
aetherloop requested a review from arcanis as a code owner August 7, 2026 19:44
@mufasacubana8-pixel

This comment was marked as off-topic.

@clemyan clemyan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Skimmed the changelogs for the updated actions. Seems fine

@MikeMcC399

Copy link
Copy Markdown
Contributor

Just wondering why this isn't getting merged, if it's approved.

@arcanis

arcanis commented Sep 15, 2026

Copy link
Copy Markdown
Member

The CI doesn't seem to have run at all

@MikeMcC399

Copy link
Copy Markdown
Contributor

The CI doesn't seem to have run at all

There was a severe GitHub incident around this time.

Perhaps @aetherloop could push an empty commit, or amend and force push?

There don't appear to have been any new commits to the master branch since Jul 29, 2026, so there is nothing new to rebase on.

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.

[CI]: outdated CI (Node.js 25 & actions/*) workflows

5 participants