You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
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).
The text was updated successfully, but these errors were encountered: