@@ -224,6 +224,8 @@ Options:
224
224
--security Demarcate the new security release as a security release [boolean]
225
225
--startLTS Mark the release as the transition from Current to LTS [boolean]
226
226
--filterLabel Filter PR by label when preparing a security release [string]
227
+ --yes Assume " yes" as answer to all prompts and run
228
+ non-interactively. [boolean] [default: false]
227
229
```
228
230
229
231
### Example
@@ -336,7 +338,7 @@ ncu-config set waitTimeMultiApproval 48
336
338
337
339
## ` git node v8 `
338
340
339
- Update or patch the V8 engine.
341
+ Update or patch the V8 engine.
340
342
This tool will maintain a clone of the V8 repository in ` ~/.update-v8/v8 `
341
343
if it's used without ` --v8-dir ` .
342
344
@@ -373,7 +375,7 @@ Options:
373
375
### ` git node v8 minor `
374
376
375
377
Compare current V8 version with latest upstream of the same major. Applies a
376
- patch if necessary.
378
+ patch if necessary.
377
379
If the ` git apply ` command fails, a patch file will be written in the Node.js
378
380
clone directory.
379
381
@@ -462,7 +464,7 @@ It will retrieve all the triaged HackerOne reports and add creates the `vulnerab
462
464
463
465
This command updates the ` vulnerabilities.json ` with target date of the security release.
464
466
Example:
465
-
467
+
466
468
``` sh
467
469
git node security --update-date=2023/12/31
468
470
```
@@ -471,7 +473,7 @@ Example:
471
473
472
474
This command creates a pre-release announcement for the security release.
473
475
Example:
474
-
476
+
475
477
``` sh
476
478
git node security --pre-release
477
479
```
0 commit comments