See e.g. nodejs/node#18990 (comment) , I'm not sure where this is documented, although there is something here:

https://github.com/nodejs/node/blob/61e3e6d56feefcd88f2baeb59c31c327835a8d90/doc/releases.md#step-3-update-any-replaceme-and-dep00xx-tags-in-the-docs

PRs that add new deprecations should have DEP00XX, which should be replaced with an actual number (e.g. DEP0100 when it lands).

PRs that add new APIs should have REPLACEME tags, that are updated with the correct version when they land in a Current release (which is then backported to LTS versions).

Things we could do:

Basic:

• Warn if there is a DEP00XX tag.
• Autoreplace DEP00XX with the next deprecation number.

Complicated:

• Check for newly added DEP???? tags (where the PR erroneously contains an already-assigned deprecation number) and warn.
  • Also autoreplace with the correct number
• Check for added: v?.?.? tags in the diff and warn.
• Check for new APIs that don't have the added: option (should maybe be a node lint instead).

cc/ @nodejs/release @nodejs/lts as the groups perhaps most likely to know about these things.