Repository navigation
Change releasing guide to consistently use "promote" over "publish" #64360
Description
Activity
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- added a commit that references this issue
on Jul 21, 2026 - added 3 commits that reference this issue
on Jul 21, 2026 - added a commit that references this issue
on Jul 29, 2026 - added a commit that references this issue
on Aug 6, 2026
I'd stick with
promoteoverpublish, that's what the flag is called in NCU, but that can be a follow upOriginally posted by @aduh95 in #64198 (review)