Skip to content

doc: mention --newVersion release script #61255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RafaelGSS wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −1
Open

doc: mention --newVersion release script #61255

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion doc/contributing/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -325,7 +325,12 @@ git node release -S --prepare --security --filterLabel v20.x
```

to automate the remaining steps until step 6 or you can perform it manually
following the below steps.
following the below steps. For semver-minors, you can pass the new version
Copy link

@Hardanish-Singh Hardanish-Singh Jan 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I just have a small nitpick on the phrasing to make it slightly more formal for the docs:

  • following the below steps. For semver-minor releases, you can pass the new version explicitly using the --newVersion argument:

Replacing 'arg' with 'argument' and 'semver-minors' with 'semver-minor releases' makes it read a bit smoother."

Copy link
Member

@NickNaso NickNaso Jan 2, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it's bettter use this form:
following the steps below. For semver-minor releases, you can pass the new version explicitly using the --newVersion argument:

Copy link

@Hardanish-Singh Hardanish-Singh Jan 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed @NickNaso

explicitly with `--newVersion` arg:
Copy link
Contributor

@aduh95 aduh95 Jan 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
explicitly with `--newVersion` arg:
explicitly with `--newVersion` flag:


```bash
git node release -S --prepare --security --filterLabel v20.x --newVersion 20.20.0
```

<details>
<summary>Security release</summary>
Expand Down
Loading