Repository navigation
Re-align to supported Node.js release lines (drop v20, add v26) #818
Description
What would you like?
Re-align to the current set of Node.js release lines
22, 24, 25
and to Node.js 26 when available
This would include removing Node.js 20 workflows from being required to pass as part of branch protection rules.
Why is this needed?
Lines 12 to 14 in 32fd150
corepack/.github/workflows/ci.yml
Lines 48 to 52 in 32fd150
define which Node.js versions are allowed / tested.
Node.js Releases provides information on the current status of each release line.
| Node.js | Status | Allowed | CI tested | Pass required |
|---|---|---|---|---|
| 20 | EOL | yes | yes | yes |
| 22 | Maintenance LTS | yes | yes | no |
| 24 | Active LTS | yes | yes | no |
| 25 | planned EOL | yes | no | - |
| 26 | Current | yes | no | - |
Other
Prerequisites
| Action | Condition |
|---|---|
| Drop Node.js 20 support | EOL on 2026-04-30 |
| Drop Node.js 25 support | EOL on 2026-06-01 |
| Add Node.js 25 to CI | PR #817 |
| Add Node.js 26 to CI | PR #817 & Node.js 26 release 2026-04-28? |
Activity
MikeMcC399 commentedon Apr 22, 2026
I can offer to submit one or more PRs for these changes when each of the prerequisites have been fulfilled, either waiting for all prerequisities or making changes in stages.
[-]Re-align to supported Node.js release lines (drop v20, add v25, then v26)[/-][+]Re-align to supported Node.js release lines (drop v20, add v26)[/+]MikeMcC399 commentedon May 6, 2026
I see that PR #831 could potentially resolve this issue, although it is not currently linked to this one.
MikeMcC399 commentedon May 15, 2026