feat: sort release blog by semver order

[himself65]

Description

See #8043

Related Issues

Fixes: #8043

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 Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Jul 30, 2025 6:44pm

[Copilot]

Pull Request Overview

This PR implements semantic version (semver) ordering for release blog posts to address issue #8043. The change ensures that release blog posts are sorted by semantic version rather than chronological order, providing a more logical ordering for users browsing release information.

Key Changes

• Added semver dependency import for version comparison
• Implemented version extraction logic from blog post titles using regex
• Modified blog post sorting to use semver ordering for release category posts

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.04%. Comparing base (b33a5a4) to head (72fd3d5).
⚠️ Report is 3 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8050   +/-   ##
=======================================
  Coverage   73.04%   73.04%           
=======================================
  Files          95       95           
  Lines        8324     8324           
  Branches      214      214           
=======================================
  Hits         6080     6080           
  Misses       2243     2243           
  Partials        1        1           

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

[mikeesto]

I don't have an opinion on what it's ordered by, but I do think it needs to be descending. The copy on the page says “latest release notes and news”, which doesn’t match showing v0.4.3 from 2011 as the first item?

[himself65]

I don't have an opinion on what it's ordered by, but I do think it needs to be descending. The copy on the page says “latest release notes and news”, which doesn’t match showing v0.4.3 from 2011 as the first item?

Yeah it's in the wrong order. but weird thing is if I reverse, the next and prev button show incorrectly

[AugustinMauroy]

LGTM !!!

[himself65]

I think for the single changelog page, the order should be by semver. in /release page, it should be by date

[himself65]

OK now it's good

[ovflowd]

I don't know any blog that does that. Can you reference more? I am really against adding very specific hacky logic that will run against every frigging blog post.

[himself65]

I don't know any blog that does that. Can you reference more? I am really against adding very specific hacky logic that will run against every frigging blog post.

Yeah I cannot find a specific one but I saw python has the selection for all changelog. maybe we could have similar

[ovflowd]

I'm fine with any other solution except the current one :)