12 GitHub stars and counting — libuv/libuv-release-tool is a JavaScript project TopGit is tracking across repositories on the platform. Tool for making libuv releases
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Command line utility for creating new releases of libuv.
Making a release
Make sure you have the most up-to-date version of this tool and the libuv
branch that will be used to create the release.
Currently, the release tool requires Node.js v12 or later. You may want to
use something like nvm to change Node versions.
Run node ./release.js --version x.x.x --dir path --remote name, where
x.x.x is the version of libuv you are creating, path is the location of
the libuv core repository on your machine, and name is the libuv core git
remote. This will perform a few tasks, such as updating the libuv AUTHORS
file if necessary. Review any changes made to libuv before continuing.
Run node ./release.js --version x.x.x --dir path --remote name --continue.
x.x.x, path, and name have the same meaning as in the previous step. The
--continue flag tells the release tool to continue work on the release started
in the previous step. If you need to cancel a release that has been started, you
can substitute --abort for --continue at any time. At this time, you should
see the CHANGELOG for the proposed release. Review the CHANGELOG for
correctness. Remove the first commit, which should mention adding the SHA to
CHANGELOG. Optionally, you may remove any commits that were made and then
reverted in this release, as they cancel each other out. Once the CHANGELOG
looks good, save the changes. You will also need to sign the release using your
GPG key.
Run node ./release.js --version x.x.x --dir path --remote name --continue
again. This updates the website, pushes the tag and branch, signs the tarball,
etc. You can verify that this step worked by checking
http://dist.libuv.org/dist/vx.x.x, which should include .tar.gz and
.tar.gz.sign files.
Create a "Now working on" commit in libuv/libuv. An example can be seen
here.
Create a new release on Github for the tag at
https://github.com/libuv/libuv/releases/new.
Optionally, make a pull request to nodejs/node to update the version of libuv.
At the time of writing, the Node.js project has automation in place to update its
libuv dependency.
TopGit's metadata for libuv/libuv-release-tool does not record a license. Most public repositories on GitHub ARE open source, but the exact terms vary — verify by opening the LICENSE file directly.
What is libuv/libuv-release-tool?
libuv/libuv-release-tool (libuv/libuv-release-tool) is a JavaScript project on GitHub. From the project's own README: Tool for making libuv releases
Where can I see libuv/libuv-release-tool in action?
The project maintains a homepage at http://libuv.org. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about libuv/libuv-release-tool?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/libuv/libuv-release-tool is the definitive source.
Read full README in the tab above.
Want a second opinion on libuv-release-tool?
Ask an AI that can read this page — one click and you get its take on libuv-release-tool.
/libuv-release-tool