GeezerVison

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodejs-org	Ready	Preview	Aug 13, 2026 7:30am

PR Summary

Low Risk
Changes are limited to MDX migration blog content with no runtime, auth, or build-logic impact.

Overview
The v16→v18 migration post now documents the @nodejs/dns-lookup-options-coercion codemod for DEP0153 (typed dns.lookup / dns.promises.lookup options), with registry link, npx command, and before/after examples for callback and promises APIs. The err-invalid-callback section heading is pluralized to Examples to match the added pattern.

The v22→v24 guide adds a one-shot npx codemod run @nodejs/v22-to-v24 command and an info AlertBox clarifying that the listed codemods are not exhaustive.

^{Reviewed by Cursor Bugbot for commit 119e023. Bugbot is set up for automated code reviews on this repo. Configure here.}

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.09%. Comparing base (28d264a) to head (692dff7).
⚠️ Report is 166 commits behind head on main.

@@            Coverage Diff             @@
##             main    #9086      +/-   ##
==========================================
+ Coverage   75.07%   75.09%   +0.02%     
==========================================
  Files         102      102              
  Lines        9070     9118      +48     
  Branches      377      377              
==========================================
+ Hits         6809     6847      +38     
- Misses       2257     2267      +10     
  Partials        4        4              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

📦 Build Size Comparison

Summary

the should be keep it's update blog post with new covered deprecation

These blog posts shouldn't change, they are point-in-time

ideally yes, but it's mean we post article only when we cover 100% of version deprecation which is take time.
and also in same idea we should have all codemod ready before LTS is landed but we have lack of maintainer

ideally yes, but it's mean we post article only when we cover 100% of version deprecation which is take time.
and also in same idea we should have all codemod ready before LTS is landed but we have lack of maintainer

In that case, a global "v22-to-v24" codemod should exist and be updated, not the blog.

am i remembering correctly that we want to pivot all of these to something more durable than a blog post?

Should we close this PR or...? cc @AugustinMauroy

IMO no we should merge it to mention everything related to this migration