Skip to content

Update GOVERNANCE.md #1082

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

Merged
merged 2 commits into from
Mar 18, 2025
Merged

Update GOVERNANCE.md #1082

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a65d12
Update GOVERNANCE.md
RafaelGSS Mar 18, 2025
66ac345
Update GOVERNANCE.md
RafaelGSS Mar 18, 2025
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
3 changes: 3 additions & 0 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,6 +159,9 @@ After the nominee's first prepared release has been promoted, the new releaser m
* Open a PR in [nodejs/release-keys](https://github.com/nodejs/release-keys) to add their GPG key via `./cli.sh add $KEY_ID`.
* Open a PR in [nodejs/Release](https://github.com/nodejs/Release) to add themselves under the "Releasers team" heading via `ncu-team sync README.md`.
* Add them to the `#nodejs-release-private` team on the OpenJS Slack.
* Configure git to sign all backport commits and release commits with the GPG key used to
sign the releases. Consider signing all commits on your local clone, e.g. with the
following command: `git config commit.gpgsign true`.

New releasers should wait at least 2 weeks after adding a GPG key to the
nodejs/node README credentials before signing a release.
Expand Down