Skip to content

doc: remove v prefix for Node.js with version references#61488

Merged
aduh95 merged 3 commits intonodejs:mainfrom
MikeMcC399:node.js-no-v-prefix
Jan 25, 2026
Merged

doc: remove v prefix for Node.js with version references#61488
aduh95 merged 3 commits intonodejs:mainfrom
MikeMcC399:node.js-no-v-prefix

Conversation

@MikeMcC399
Copy link
Copy Markdown
Contributor

@MikeMcC399 MikeMcC399 commented Jan 23, 2026

Situation

According to the Node.js documentation style guide > Version references section, version references using the text "Node.js" should be written without a v prefix. Some references are not using this format (14 out of 55).

Change

Change occurrences of Node.js version references to conform to the style guide, for example:

Before After
Node.js v24 Node.js 24
Node.js v0.8 Node.js 0.8
Node.js v11.0.0 Node.js 11.0.0

The majority of references were already correct.

Usage in CHANGELOG files is not touched, since these are considered immutable historical records.

doc/contributing/releases.md is also left unchanged. This should preferably be reviewed and updated separately by the release team to check and correct usage of "Node.js v" consistently.

Edit for clarification: This PR is only concerned with the combination text such as "Node.js 24.13.0".

Other uses with v like the output of the CLI command node --version "v24.13.0" or API documentation "Added in: v24.13.0" are OK and not impacted.

This is also in line with blog post release notices on https://nodejs.org/en/blog/release

image

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. i18n-api Issues and PRs related to the i18n implementation. icu Issues and PRs related to the ICU dependency. tools Issues and PRs related to the tools directory.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants