Skip to content

Migrate node to v22#2838

Merged
gerteck merged 5 commits intoMarkBind:masterfrom
Harjun751:migrate-node-to-22
Feb 20, 2026
Merged

Migrate node to v22#2838
gerteck merged 5 commits intoMarkBind:masterfrom
Harjun751:migrate-node-to-22

Conversation

@Harjun751
Copy link
Contributor

@Harjun751 Harjun751 commented Feb 19, 2026

What is the purpose of this pull request?

  • Documentation update
  • Bug fix
  • Feature addition or enhancement
  • Code maintenance
  • DevOps
  • Improve developer experience
  • Others, please explain:

Overview of changes:

  • Update variables in docs to use v22
  • Update CI script to use node v22

Anything you'd like to highlight/discuss:

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: ☑️

  • Updated the documentation for feature additions and enhancements
  • Added tests for bug fixes or features
  • Linked all related issues
  • No unrelated changes

Reviewer checklist:

Indicate the SEMVER impact of the PR:

  • Major (when you make incompatible API changes)
  • Minor (when you add functionality in a backward compatible manner)
  • Patch (when you make backward compatible bug fixes)

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):

  • To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

  • what was the old feature that was made obsolete
  • any replacement feature (if any), and
  • how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

@codecov
Copy link

codecov bot commented Feb 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.07%. Comparing base (bc56f0a) to head (b284fce).
⚠️ Report is 1 commits behind head on master.

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Harjun751 Harjun751 requested a review from a team February 19, 2026 12:04
@gerteck
Copy link
Member

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
Copy link
Contributor Author

Alright the docs list the node version as 22. Is there any part I missed?

@gerteck
Copy link
Member

gerteck 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 👍

@gerteck gerteck merged commit b05d3a7 into MarkBind:master Feb 20, 2026
9 checks passed
@github-actions github-actions bot added the r.Major Version resolver: increment by 1.0.0 label Feb 20, 2026
@gerteck
Copy link
Member

gerteck commented Feb 20, 2026

Devdocs now show Node v22 or higher 🎉

https://markbind.org/devdocs/devGuide/development/settingUp.html#prerequisites

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

r.Major Version resolver: increment by 1.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments