nodejs / nodejs/Release

Changed process for releaser key updates in `docker-node`

Open Beginner friendly
#1,181 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
4.4k
Forks
675
Avg merge
22h 29m
Merged PRs (30d)
1

Description

Situation

The GOVERNANCE > Adding new releasers documentation section instructs a new releaser to:

Open a PR in nodejs/docker-node to add their GPG key to node.keys.

The process to maintain releasers keys in the nodejs/docker-node repo has been partially automated, so that manual PR creation by a new releaser (or for any other change in releaser keys) is no longer necessary.

If a PR is created, the @nodejs/releasers team is included as reviewers.

Suggestion

Since there is no longer any proactive manual action required in the nodejs/docker-node repo from releasers when keys change, the reference to manually opening a PR could be removed.

It could be replaced with a description to say that the keys are automatically checked once a week on Mondays.

cc: @nschonni

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the “Adding new releasers” section in GOVERNANCE.md and compare its instructions with the current automated process in nodejs/docker-node. Remove the manual PR instruction and document that releaser keys are checked automatically each Monday; confirm the rendered Markdown accurately reflects the updated process.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
88/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.