Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 839f026

Browse filesBrowse files
TrottMylesBorins
Trott
authored and
MylesBorins
committed
doc: rename README section for Release Keys
The section of the README currently labeled "Release Team" isn't about the team much and is very much about the keys. Rename it "Release Keys" so that it's purpose matches it's name. PR-URL: #23927 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me>
1 parent 565f4ca commit 839f026
Copy full SHA for 839f026

File tree

Expand file treeCollapse file tree

1 file changed

+7
-7
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+7
-7
lines changed
Open diff view settings
Collapse file

‎README.md‎

Copy file name to clipboardExpand all lines: README.md
+7-7Lines changed: 7 additions & 7 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ The Node.js project uses an [open governance model](./GOVERNANCE.md). The
3131
* [Current Project Team Members](#current-project-team-members)
3232
* [TSC (Technical Steering Committee)](#tsc-technical-steering-committee)
3333
* [Collaborators](#collaborators)
34-
* [Release Team](#release-team)
34+
* [Release Keys](#release-keys)
3535
* [Contributing to Node.js](#contributing-to-nodejs)
3636

3737
## Support
@@ -81,7 +81,7 @@ your expectations.
8181
changes. Use with caution.
8282

8383
Current and LTS releases follow [Semantic Versioning](https://semver.org). A
84-
member of the [Release Team](#release-team) signs each Current and LTS release.
84+
member of the Release Team [signs](#release-keys) each Current and LTS release.
8585
For more information, see the
8686
[Release README](https://github.com/nodejs/Release).
8787

@@ -133,9 +133,9 @@ $ grep node-vx.y.z.tar.gz SHASUMS256.txt | sha256sum -c -
133133

134134
For Current and LTS, the GPG detached signature of `SHASUMS256.txt` is in
135135
`SHASUMS256.txt.sig`. You can use it with `gpg` to verify the integrity of
136-
`SHASUM256.txt`. You will first need to import all the GPG keys of individuals
137-
authorized to create releases. They are at the bottom of this README under
138-
[Release Team](#release-team). To import the keys:
136+
`SHASUM256.txt`. You will first need to import
137+
[the GPG keys of individuals authorized to create releases](#release-keys). To
138+
import the keys:
139139

140140
```console
141141
$ gpg --keyserver pool.sks-keyservers.net --recv-keys DD8F2338BAE7501E3DD5AC78C273792F7D83545D
@@ -555,9 +555,9 @@ For information about the governance of the Node.js project, see
555555
Collaborators follow the [COLLABORATOR_GUIDE.md](./COLLABORATOR_GUIDE.md) in
556556
maintaining the Node.js project.
557557

558-
### Release Team
558+
### Release Keys
559559

560-
Node.js releases are signed with one of the following GPG keys:
560+
GPG keys used to sign Node.js releases:
561561

562562
* **Colin Ihrig** &lt;cjihrig@gmail.com&gt;
563563
`94AE36675C464D64BAFA68DD7434390BDBE9B9C5`

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.