Repository navigation
Node.js API v18.x does not mark 18 LTS but does mark 12 LTS #45316
Description
Activity
Both components of this issue are resolved now that the header says 18.12.1.
It could be that the documentation is being built before the LTS status is updated. I notice that 12.x was only marked end of life 9 days ago (see #45186), even though support was only planned until 30 April 2022.
Does it make sense to mark a release LTS based solely on date, before the first release after the LTS date? If not, and the build script pulls its information from the changelog, then the build script can't see the LTS status before it's published.
Maybe, rather than applying regular expressions to the changelog, it could source the LTS status from https://github.com/nodejs/Release/blob/main/schedule.json
@nodejs/releasers
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Affected URL(s)
https://nodejs.org/docs/latest-v18.x/api/index.html
Description of the problem
Under "Other versions", "18.x" is not "18.x LTS" but should be.
"12.x LTS" should be just "12.x".
Currently the header shows v18.12.0. Once it's updated to v18.12.1, it'll be interesting to check again and see if the issue resolves itself (18.12.0 is the first LTS release of the 18.x series).