a522da3935
There is a better maintained script in node-code-utils which properly bumps the version numbers for each of the LTS branches, which is more useful. Node collaborators also use this script, so it will make backports more uniform. Change-Id: If5449b8a801c4bd14f39d59b7af52cc959989be7 Reviewed-on: https://chromium-review.googlesource.com/c/1328927 Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#57393} |
||
---|---|---|
.. | ||
testdata | ||
build_gn.py | ||
fetch_deps.py | ||
node_common.py | ||
README.md | ||
test_update_node.py | ||
update_node.py |
Node.js Backports
We no longer maintain our own backport script.
For backporting V8 changes to Node.js, there is a useful script in
node-core-utils. You can use the git node v8 backport
command, which will
bump the necessary V8 version numbers depending on the specific branch.
See the Node.js documentation on V8 backports for a guide.