Uh oh!
There was an error while loading. Please reload this page.
Migrate node to v22 - #2838
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## master #2838 +/- ##
=======================================
Coverage 72.07% 72.07% =======================================
Files 134 134 Lines 7410 7410 Branches 1650 1555 -95 =======================================
Hits 5341 5341 Misses 1941 1941 Partials 128 128 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
gerteck
commented
Feb 19, 2026
Looks good, but need you to update the dev docs! (Step 6 of https://markbind.org/devdocs/devGuide/development/migratingNodeJs.html) |
Harjun751
commented
Feb 20, 2026
Alright the docs list the node version as 22. Is there any part I missed? |
Nope, I don't think so. looks good 👍 |
Uh oh!
There was an error while loading. Please reload this page.
gerteck
commented
Feb 20, 2026
Devdocs now show Node v22 or higher 🎉 https://markbind.org/devdocs/devGuide/development/settingUp.html#prerequisites |
What is the purpose of this pull request?
Overview of changes:
Anything you'd like to highlight/discuss:
markbind deployworks as expected (see test deployment here) (NOTE: this was done after applying the patch in Fixmarkbind serveregression #2837 manually since it wasn't merged yet)Related PRs:
Update markbind-action to node v22
Update init-typical-netlify configs to node v22
Update init-minimal-netlify configs to node v22
Testing instructions:
Proposed commit message: (wrap lines at 72 characters)
Migrate MarkBind to Node.js v22
MarkBind uses node18.
Node18's last update was Mar 2025, and
is now EOL.
Change node version to 22 (LTS).
Skip version 20 as v20 is EOL in 2 months.
Checklist: ☑️
Reviewer checklist:
Indicate the SEMVER impact of the PR:
At the end of the review, please label the PR with the appropriate label:
r.Major,r.Minor,r.Patch.Breaking change release note preparation (if applicable):