Roll Node.js floor back to >= 24 (Active LTS) — closes #7779#7781
Conversation
Closes #7779. #7779 originally proposed bumping past the Node 25 stop-gap to Node 26. After re-checking the release schedule, the cleaner LTS target is actually Node 24: - Node 24 (Krypton) is currently in Active LTS, supported until ~May 2028. - Node 25 hit end-of-life on April 10 2026 — the floor merged in #7752 / #7749 / #7754 a day ago ships an already-EOL major. - Node 26 was released May 5 2026 and does not enter Active LTS until October 2026. So this PR reverts the Node 25 ratchet from those three PRs and lands on Node 24 — Etherpad's runtime floor stays on a supported LTS for the next ~2 years. Runtime / infra - `package.json` + `src/package.json`: `engines.node` `>=25.0.0` -> `>=24.0.0` - `bin/functions.sh`, `bin/installer.sh`, `bin/installer.ps1`: `REQUIRED_NODE_MAJOR` 25 -> 24 - `Dockerfile`: `node:25-alpine` -> `node:24-alpine` (both stages). Corepack-via-npm workaround is intentionally kept: it works on Node 24 (which still ships corepack) and on Node 25+ (which doesn't), so the same recipe survives the next LTS bump without churn. Comments reworded accordingly. - `snap/snapcraft.yaml`: pinned `NODE_VERSION` 25.9.0 -> 24.15.0; design notes + corepack comment adjusted - `packaging/nfpm.yaml`: `nodejs (>= 25)` -> `nodejs (>= 24)` in top-level depends + deb/rpm overrides - `packaging/bin/etherpad`: comment matches the new pin - `packaging/README.md`: build prereqs + apt install snippet point at `node_24.x`; the long-stale "engines.node floor is 20" line is fixed while we're here - `.github/workflows/*.yml`: setup-node `node-version` 25 -> 24 across every workflow; backend / frontend-admin / upgrade matrices `[25]` -> `[24]` - `.github/workflows/deb-package.yml`: `NODE_MAJOR=25` + `node_25.x` smoke-test installer -> 24 - `bin/plugins/lib/npmpublish.yml`: 25 -> 24 (template propagates to the ~80 ether/* plugins via update-plugins workflow) Docs - `README.md`: install one-liner + Requirements -> Node.js >= 24 - `doc/npm-trusted-publishing.md`: runner requirement -> Node 24 - `doc/plugins.md` / `doc/plugins.adoc`: plugin metadata example `engines.node` -> `">=24.0.0"` @types/node is left at ^25.8.0 — newer type definitions cover Node 24 runtime fine and avoid an unnecessary lockfile churn. Companion homepage one-liner change to follow on ether/ether.github.com. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
Review Summary by QodoDowngrade Node.js floor to >= 24 (Active LTS) — closes #7779
WalkthroughsDescription• Downgrade Node.js minimum from 25 to 24 (Active LTS) • Update all CI workflows to test against Node 24 • Revise Docker, Snap, and package configs for Node 24 • Fix stale documentation references to Node version Diagramflowchart LR
A["Node 25<br/>EOL Apr 2026"] -->|"Revert to"| B["Node 24<br/>Active LTS<br/>until May 2028"]
B -->|"Update"| C["Runtime Config<br/>package.json<br/>Dockerfile<br/>Snap/nfpm"]
B -->|"Update"| D["CI Workflows<br/>All test matrices<br/>setup-node versions"]
B -->|"Update"| E["Documentation<br/>README<br/>Plugin examples<br/>Build guides"]
File Changes1. bin/functions.sh
|
Plugin code is overwhelmingly ace-hook glue and rarely uses Node-version- specific APIs, so plugin engines.node should reflect the plugin's own requirements, not track core. Showing core's 24-floor in the example encouraged plugin authors to blindly copy a tighter pin than necessary and locked plugins out of being installable on older Etherpad/Node deployments. Use the most-recent Node LTS that has actually reached EOL (20 -> EOL April 2026) as the example floor, i.e. >=22. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
CI green across the board (17 pass, 0 failures, 10 path-ignored skips on doc-only paths) — including |
Companion to ether/etherpad#7781 (closes ether/etherpad#7779). Node 25 hit end-of-life on April 10 2026, so the runtime floor #402 set on the homepage points at an already-EOL major. Roll back to Node 24, which is the current Active LTS (supported until ~May 2028). Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Etherpad has settled back on Node 24 as its minimum supported runtime (ether/etherpad#7781), so ueberDB's recent bump to >=25 (#961) is now ahead of its primary consumer. Lower `engines.node` and the CI runner back to 24 to keep the library in lock-step. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Summary
Closes #7779.
#7779 originally proposed bumping past the Node 25 stop-gap to Node 26. After re-checking the release schedule, the cleaner LTS target is actually Node 24:
So this PR reverts the Node 25 ratchet from those three PRs and lands on Node 24 — Etherpad's runtime floor stays on a supported LTS for the next ~2 years.
Runtime / infra
package.json+src/package.json:engines.node>=25.0.0->>=24.0.0bin/functions.sh,bin/installer.sh,bin/installer.ps1:REQUIRED_NODE_MAJOR25 -> 24Dockerfile:node:25-alpine->node:24-alpine(both stages). Corepack-via-npm workaround is intentionally kept: it works on Node 24 (which still ships corepack) and on Node 25+ (which doesn't), so the same recipe survives the next LTS bump without churn. Comments reworded accordingly.snap/snapcraft.yaml: pinnedNODE_VERSION25.9.0 -> 24.15.0; design notes + corepack comment adjustedpackaging/nfpm.yaml:nodejs (>= 25)->nodejs (>= 24)in top-level depends + deb/rpm overridespackaging/bin/etherpad: comment matches the new pinpackaging/README.md: build prereqs + apt install snippet point atnode_24.x; the long-stale "engines.node floor is 20" line is fixed while we're here.github/workflows/*.yml: setup-nodenode-version25 -> 24 across every workflow; backend / frontend-admin / upgrade matrices[25]->[24].github/workflows/deb-package.yml:NODE_MAJOR=25+node_25.xsmoke-test installer -> 24bin/plugins/lib/npmpublish.yml: 25 -> 24 (template propagates to the ~80 ether/* plugins via update-plugins workflow)Docs
README.md: install one-liner + Requirements -> Node.js >= 24doc/npm-trusted-publishing.md: runner requirement -> Node 24doc/plugins.md/doc/plugins.adoc: plugin metadata exampleengines.node->">=24.0.0"Notes
@types/nodeleft at^25.8.0— newer type definitions cover Node 24 runtime fine and avoid an unnecessary lockfile churn.engines.node(src/node/utils/NodeVersion.ts), so no source changes are needed.ether/ether.github.com.engines.nodesweep: I'll retarget it so plugins float on a permissive>=22floor (or keep their existing one if already higher) rather than tightly tracking core — this leaves plugins installable on older Etherpad/Node combinations and reduces churn.Test plan
docker build .succeeds againstnode:24-alpine.core24withNODE_VERSION=24.15.0.apt-get install nodejsinside deb-package smoke step pulls 24.x via NodeSourcenode_24.x.🤖 Generated with Claude Code