build(node.js)!: pf-3843 remove 20 support#169
Merged
Conversation
a56afd0 to
498123b
Compare
Member
Author
|
Need to make sure we update any refs added by #173 |
Member
Author
|
This moves in AFTER a planned |
72cdf2d to
67676e9
Compare
Member
Author
615b152 to
797078c
Compare
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is it?
Notes
2majorscheduled for merge AFTER chore(release): 1.0.1 #168 and a potential1.1.0or1.0.2release[ ] scheduled for after ci: pf-4128 contribution policy workflow #194 and potentially after docs(contributing): pf-4128 automation, testing standards #19326support is scheduled for pf-mcp direct support later this year, but it's non-blocking if someone wants to use it. review our scheduleUnit test check
$ npm install$ npm test20is removed from integration checks leaving only22and24.Updates issue/story
pf-3843
closes #142