Thank you for your contribution. Here are a set of guidelines for contributing to the docker-node project.
New Node.js releases are released as soon as possible.
New NPM releases are not tracked. We simply use the NPM version bundled in the corresponding Node.js release.
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.
- Every 15 minutes, the workflow within the nodejs/docker-node repo checks for new versions of Node.js published to the website's
index.jsonfile.- If found, it also checks for an unofficial musl/Alpline build.
- If found, the update script runs
- The workflow opens a pull request is opened either by nodejs-github-bot. In some cases, this PR is manually created, such as new major releases.
- Another workflow detects the merger of these pull requests and opens a pull request to docker-library/official-images.
- The official images are built and published according to docker's process, resulting in the new images being available on Docker Hub.
If you'd like to help us by submitting a PR for a version update, please do the following:
- Fork this project.
- Clone the forked repository.
- Create a branch for the update PR. For example,
git checkout main; git checkout -b version-update. - 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. - Commit the modified files to the
version-updatebranch and push the branch to your fork. - Create a PR to merge the branch from your fork into this project's default branch..
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.