Long and short deprecation links

[MikeMcC399]

URL:

https://nodejs.org/docs/latest-v26.x/api/deprecations.html

Browser Name:

Google Chrome

Browser Version:

148.0.7778.97

Operating System:

Windows 11 25H2

How to reproduce the issue:

Browse to https://nodejs.org/docs/latest-v26.x/api/deprecations.html
Right-click on DEP001 and copy link address
https://nodejs.org/docs/latest-v26.x/api/deprecations.html#dep0001-httpoutgoingmessageprototypeflush

Browse to https://nodejs.org/docs/latest-v24.x/api/deprecations.html
Right-click on DEP001 and copy link address
https://nodejs.org/docs/latest-v24.x/api/deprecations.html#DEP0001

---

In the Table of contents for API Deprecated APIs, Node.js 22 & 24 use a simple short link target:

Node.js	DEP0001
22.22.22	#DEP0001
24.15.0	#DEP0001
25.19.0	deprecations.html#dep0001-httpoutgoingmessageprototypeflush
26.1.0	deprecations.html#dep0001-httpoutgoingmessageprototypeflush

Moving to the detail section for the deprecation, for example:

https://nodejs.org/docs/latest-v26.x/api/deprecations#DEP0001 and then clicking on the # symbol directs to the long bookmark:

https://nodejs.org/docs/latest-v26.x/api/deprecations.html#dep0001-httpoutgoingmessageprototypeflush

This is the same for each of the supported versions.

Would it be possible to standardize on only using the short bookmark form, like #DEP0001 instead of having a mixture of short and long bookmarks?

If I copy the link to post somewhere else, like in another repository, it feels more robust to use just the short link, so I would prefer that one. It confuses me to have two different types of links, also depending on which versions of Node.js I'm referring to.

#750 is an earlier related issue that was resolved through #752