From 9718af32025f385ff171467ae83b83ed69d23a05 Mon Sep 17 00:00:00 2001 From: Muhtasim-Munif-Fahim Date: Thu, 9 Jul 2026 01:22:50 +0600 Subject: [PATCH] doc: use promote wording in release guide --- doc/contributing/releases.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index 7f96cba0511c43..2099ea52dd8ed8 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -40,7 +40,7 @@ official release builds for Node.js, hosted on . ## Who can make a release? There is a distinction between individuals who can "prepare" a release by -adding the commits to the branches in GitHub and those who can "publish" the +adding the commits to the branches in GitHub and those who can "promote" the releases to nodejs.org. Individuals who are Members of the @@ -49,12 +49,12 @@ Individuals who are Members of the releases including creating the proposal branches which will be discussed later in this document. -Authorization to publish releases is given by the Node.js TSC. This is -required to publish a release after it has been prepared. If you are working +Authorization to promote releases is given by the Node.js TSC. This is +required to promote a release after it has been prepared. If you are working on preparing a release for the first time you will be able to do most of the steps as a member of the backporters team and have someone else who is already onboarded promote the release on your behalf. Once authorized by the -TSC as a releaser, an individual will require the following to publish +TSC as a releaser, an individual will require the following to promote releases themselves: ### 1. Jenkins release access