Skip to content

build(node.js)!: pf-3843 remove 20 support#169

Merged
cdcabrera merged 2 commits into
patternfly:mainfrom
cdcabrera:20260427-build
May 21, 2026
Merged

build(node.js)!: pf-3843 remove 20 support#169
cdcabrera merged 2 commits into
patternfly:mainfrom
cdcabrera:20260427-build

Conversation

@cdcabrera
Copy link
Copy Markdown
Member

@cdcabrera cdcabrera commented Apr 27, 2026

What is it?

  • build(node.js)!: pf-3843 remove 20 support
    • audit, publishing baselines moved to node.js 24
    • build, engine, moved to node.js 22 minimum
    • docs, references moved to node.js 22
    • tests, e2e, cleaned node.js 20 checks

Notes

BREAKING CHANGE: Minimum supported Node.js is now 22, previously 20.
MCP clients and integrations running Node.js 20 will fail to start
on @latest.

To migrate:

  • Either upgrade Node.js to a minimum of 22 LTS.
  • Or pin the server configuration to a Node.js 20-compatible release

See usage docs for pinned configuration examples.

Unit test check

  1. update the NPM packages with $ npm install
  2. $ npm test
  3. confirm tests come back clean
    • verify that 20 is removed from integration checks leaving only 22 and 24.

Updates issue/story

pf-3843
closes #142

@cdcabrera cdcabrera added the hold review needed label Apr 27, 2026
@cdcabrera cdcabrera added the breaking a breaking change label Apr 30, 2026
@cdcabrera
Copy link
Copy Markdown
Member Author

Need to make sure we update any refs added by #173

@cdcabrera
Copy link
Copy Markdown
Member Author

cdcabrera commented May 1, 2026

This moves in AFTER a planned 1.1.0 or 1.0.2 release.

@cdcabrera cdcabrera force-pushed the 20260427-build branch 2 times, most recently from 72cdf2d to 67676e9 Compare May 4, 2026 19:51
@cdcabrera
Copy link
Copy Markdown
Member Author

cdcabrera commented May 12, 2026

And a new requirement. #194 and potentially #193 need to roll in first since they affect the yml configs follows #200

@cdcabrera cdcabrera force-pushed the 20260427-build branch 2 times, most recently from 615b152 to 797078c Compare May 21, 2026 15:06
@cdcabrera cdcabrera removed the hold review needed label May 21, 2026
@cdcabrera cdcabrera marked this pull request as ready for review May 21, 2026 15:06
@cdcabrera
Copy link
Copy Markdown
Member Author

Review indicates we need to provide a "how to pin the server." By showing that we still support Node.js 20 with pinning we potentially reduce "bug" reports.

* audit, move dep audit, publishing baselines moved to node.js 24
* build, engine, moved to node.js 22 minimum
* cli, node.js version copy, pin server version to support older node.js
* docs, references moved to node.js 22
* package, min engine version, cleaned test scripts
* src, drop node.js 20 reference
* e2e, cleaned node.js 20 checks, left itSkip, envNodeVersion

BREAKING CHANGE: Minimum supported Node.js is now 22, previously 20.
MCP clients and integrations running Node.js 20 will fail to start
on `@latest`.

To migrate:
- Either upgrade Node.js to a minimum of 22 LTS.
- Or pin the server configuration to a Node.js 20-compatible release

See usage docs for pinned configuration examples.
@cdcabrera cdcabrera merged commit 589a390 into patternfly:main May 21, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking a breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update min Node.js engine requirements

1 participant