node-core-utils
node-core-utils copied to clipboard
CLI tools for Node.js Core collaborators
Since the remark-lint rules in https://github.com/nodejs/remark-preset-lint-node enforce this, it would be good to be consent with the inserted sections, so they don't need to be ignored in the READMEs that...
I reach to `node-core-utils` for automating the LTS release commit but I couldn't get it to work due to the lack of a proper usage example. I'm adding examples to...
fix: https://github.com/nodejs/node-core-utils/issues/559 test pr: https://github.com/nodejs/node/pull/44986 Hopefully this will make us test v8 easier :) local test ``` node bin/ncu-ci.js run 44986 ``` currently I run into Jenkins credentials invalid. But...
* node-fetch not working on 18 (maybe only with proxy) * proxy only support http, sock5 not working
:robot: I have created a release *beep* *boop* --- ## [2.1.0](https://github.com/nodejs/node-core-utils/compare/v2.0.1...v2.1.0) (2022-10-12) ### Features * add --since option to ncu-ci ([#649](https://github.com/nodejs/node-core-utils/issues/649)) ([e01ca12](https://github.com/nodejs/node-core-utils/commit/e01ca12368677e1f8f72f97c4170b386cb250fb8)) ### Bug Fixes * only parse commit messages...
I started investigating https://github.com/nodejs/node/issues/44805 when taking a look at https://github.com/nodejs/reliability/issues/388: | Reason | sequential/test-watch-mode-inspect | | - | :- | | Type | JS_TEST_FAILURE | | Failed PR | 9...
:robot: I have created a release *beep* *boop* --- ## [4.5.0](https://github.com/nodejs/node-core-utils/compare/v4.4.0...v4.5.0) (2024-04-04) ### Features * request cve automatically ([#777](https://github.com/nodejs/node-core-utils/issues/777)) ([8a04848](https://github.com/nodejs/node-core-utils/commit/8a048483b23c509e2d12afd1b1975f23fd647046)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
Pos release blogpost cc @RafaelGSS
Fixes: https://github.com/nodejs-private/security-release/issues/9 Also we prompt for the release date for the issue, it makes sense to add it to the vulnerabilities.json, if it doesnt change you dont have to do...
So that we get records about tests that are already marked as flaky as well. This should probably only be done for the walk command.