Specify whether minor versions are current are LTS

[hyunbinseo]

Enter your suggestions in details:

Seeing the tsdown's release note, I was wondering

• Why drop certain versions of 24?
• Why is this breaking but in patch?

Then I remembered, Node.js 24 started out as current then was converted to LTS.

But the release page's modal doesn't pin point when this change was made:

So I had to dig through the blog's release articles to find out.

https://nodejs.org/ko/blog/release/v24.11.0

This process was rather cumbersome and required background knowledge.

[aduh95]

FWIW I don't think it should be relevant whether a given release was published as Current or LTS as soon as a more recent release on that line exists. My reading of the situation is that we had a hard time to understand tsdown's change because it was completely arbitrary: 24.10.0 and 24.11.0 have the exact same feature set, you cannot support 24.11.0 without also supporting 24.10.0. IMO dropping version support should be feature based (i.e. the most modern feature I need is only available in such version set, so that's what I support), or simply target whatever is the latest semver-minor on all supported release lines.

If you want Long-Term-Support, we need to stay up-to-date, i.e. be on 24.18.0; I wouldn't want the website to give a false impression that it would be somewhat OK to chose to use 24.11.0 because it was released as LTS (almost a year ago).

[hyunbinseo]

I always use the latest Node.js LTS. And I believe it's important to stay up to date.

It would just be nice if the current ➡️ LTS switch was evident on the website. (e.g. horizontal divider in the table)