GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — doc: update security release prepare command · nodejs/node@9b92fdc

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • doc/contributing
    • releases.md
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎doc/contributing/releases.md‎

Copy file name to clipboardExpand all lines: doc/contributing/releases.md
+9-3Lines changed: 9 additions & 3 deletions
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -377,22 +377,28 @@ git checkout -b v1.2.3-proposal upstream/v1.x-staging
377377
You can also run:
378378

379379
```bash
380-
git node release -S --prepare --security=../vulnerabilities.json --filterLabel vX.x
380+
git node release -S --prepare --security=../security-release
381381
```
382382

383+
The `--security` flag takes the path to your clone of the `security-release`
384+
repository (or directly to a `vulnerabilities.json` file). The reports and
385+
dependency updates to cherry-pick are selected automatically from each entry's
386+
`affectedVersions` mapping for the release line you are on, and the matching
387+
`CVE-ID` trailers are added from the same file.
388+
383389
Example:
384390

385391
```bash
386392
git checkout v20.x
387-
git node release -S --prepare --security=../vulnerabilities.json --filterLabel v20.x
393+
git node release -S --prepare --security=../security-release
388394
```
389395

390396
to automate the remaining steps until step 6 or you can perform it manually
391397
following the below steps. For semver-minors, you can pass the new version
392398
explicitly with `--newVersion` arg:
393399

394400
```bash
395-
git node release -S --prepare --security=../vulnerabilities.json --filterLabel v20.x --newVersion 20.20.0
401+
git node release -S --prepare --security=../security-release --newVersion 20.20.0
396402
```
397403

398404
<details>

0 commit comments

Comments
0 (0)
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.