fix: semantic version in release blog posts

[aduh95]

Description

SImilar to #7998, our guidelines indicates we should be using Node.js x.y.z instead of Node.js vx.y.z.

Refs: https://github.com/nodejs/node/blob/668e52339261ec21c7388884620987914c833395/doc/README.md#L220-L222
Fixes: nodejs/node#61231

Validation

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run pnpm format to ensure the code follows the style guide.
• I have run pnpm test to check if all tests are passing.
• I have run pnpm build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
nodejs-org	Ready	Preview	Jan 6, 2026 4:55pm

[github-actions]

👋 Codeowner Review Request

The following codeowners have been identified for the changed files:

Team reviewers: @nodejs/releasers

Please review the changes when you have a chance. Thank you! 🙏

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.66%. Comparing base (8c5a7dd) to head (1afcb32).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8520      +/-   ##
==========================================
- Coverage   74.70%   74.66%   -0.05%     
==========================================
  Files         102      102              
  Lines        8956     8956              
  Branches      305      306       +1     
==========================================
- Hits         6691     6687       -4     
- Misses       2263     2267       +4     
  Partials        2        2              

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

[avivkeller]

Can we leave the previous blog posts the same, and only start applying this to future posts?

[avivkeller]

I'll update @node-core/remark-lint with this new requirement, as well

[aduh95]

Can we leave the previous blog posts the same, and only start applying this to future posts?

Why? We did update old posts in #7998, I don't think it broke anything

[avivkeller]

That change was a bit different, IMO. This is referring to the actual version, and I think it's important to maintain consistency, however, I'm not going to force it, if you think this is best, go ahead

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[aduh95]

This is referring to the actual version

I think there's a misunderstanding, the actual version does not change, e.g. v0.10.0 has always been Node.js 0.10.0, before or after this change. This PR is simply updating the blog posts to match our style guide, it is not a renaming nor a new requirement (very similar to #7998).

[MattIPv4]

Has the tooling that generates these posts been updated?

[aduh95]

Has the tooling that generates these posts been updated?

Yes, as you can see in the diff (https://github.com/nodejs/nodejs.org/pull/8520/files#diff-873e2ee117570f0836a600113925cbeb0929ece48acb9df0076d06b54f17d0e4)