Skip to content

Commit 8bcc171

Browse files
Merge pull request nodejs#1193 from clayzermk1/version-update-instructions
Add instructions for submitting a version update PR
2 parents 2e7cc02 + 494bbc0 commit 8bcc171

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

CONTRIBUTING.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,17 @@ New **NPM** releases are not tracked. We simply use the NPM version bundled in t
1010

1111
**Yarn** is updated to the latest version only when there is a new Node.js SemVer PATCH release (unless Yarn has received a security update), and it's updated only in the branch with the new release, preferably in the same PR. The `update.sh` script does this automatically when invoked with a specific branch, e.g. `./update.sh 6.10`.
1212

13+
### Submitting a PR for a version update
14+
15+
If you'd like to help us by submitting a PR for a version update, please do the following:
16+
17+
1. [Fork this project.](https://help.github.com/en/github/getting-started-with-github/fork-a-repo)
18+
1. [Clone the forked repository.](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/cloning-a-repository)
19+
1. Create a branch for the update PR. For example, `git checkout master; git checkout -b version-update`.
20+
1. Run `./update.sh`. You can see additional options by using accessing the built-in help documentation with `./update.sh -h`. This script will automatically update the appropriate files with the latest versions and checksums.
21+
1. Commit the modified files to the `version-update` branch and push the branch to your fork.
22+
1. [Create a PR to merge the branch from your fork into this project's master branch.](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
23+
1324
## Adding dependencies to the base images
1425

1526
NodeJS is a big ecosystem with a variety of different use cases. The docker images for node are designed to provide the minimum for running core node. Additional dependencies (including dependencies for npm or yarn such as git) will not be included in these base images and will need to be included in descendent image.

0 commit comments

Comments
 (0)