You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Change releasing guide to consistently use "promote" over "publish" #64360
It may need a preamble in the document to define what "publish" and "promote" mean, if they are interchangeable or if they mean different things.
It looks like "Create the release on GitHub" would still need the instruction "Click on the "Publish release" button." since that is what the GitHub UI uses.
Creating the release on GitHub is something that's done after the release is promoted. GitHub UI is not at all involved in promoting a release.
I think we should not use "publish" at all when referring to a Node.js release, we don't have a use for it AFAICT.
Reacted by Mike McCready, Stewart X Addison and Marco Ippolito
Activity
MikeMcC399 commentedon Jul 9, 2026
It may need a preamble in the document to define what "publish" and "promote" mean, if they are interchangeable or if they mean different things.
It looks like "Create the release on GitHub" would still need the instruction "Click on the "Publish release" button." since that is what the GitHub UI uses.
aduh95 commentedon Jul 9, 2026
Creating the release on GitHub is something that's done after the release is promoted. GitHub UI is not at all involved in promoting a release.
I think we should not use "publish" at all when referring to a Node.js release, we don't have a use for it AFAICT.
doc: use promote wording in release guide
doc: use promote wording in release guide
doc: use promote wording in release guide
doc: use promote wording in release guide
doc: use promote wording in release guide
doc: use promote wording in release guide