v16.8.0 release proposal

.eslintignore

@@ -4,7 +4,7 @@ test/addons/??_*
 test/fixtures
 test/message/esm_display_syntax_error.mjs
 tools/icu
-tools/lint-md.js
+tools/lint-md.mjs
 tools/node-lint-md-cli-rollup/dist
 benchmark/tmp
 doc/**/*.js

.github/CODEOWNERS

@@ -97,6 +97,12 @@
 /doc/guides/adding-new-napi-api.md @nodejs/n-api
 /doc/api/n-api.md @nodejs/n-api
 
+# gyp
+
+*.gyp @nodejs/gyp
+*.gypi @nodejs/gyp
+/tools/gyp/**/* @nodejs/gyp
+
 # WASI
 /deps/uvwasi/ @nodejs/wasi
 /doc/api/wasi.md @nodejs/wasi

.github/workflows/authors.yml

@@ -0,0 +1,22 @@
+name: "authors update"
+on:
+  workflow_dispatch:
+
+jobs:
+  authors_update:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          fetch-depth: '0' # this is required to actually get all the authors
+      - run: "tools/update-authors.js" # run the AUTHORS tool
+      - uses: gr2m/create-or-update-pull-request-action@v1 # create a PR or update the Action's existing PR
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          title: "meta: update AUTHORS"
+          body: "If this PR exists, there's presumably new additions to the AUTHORS file. This is an automatically generated PR by the `authors.yml` GitHub Action, which runs `tools/update-authors.js` and submits a new PR or updates an existing PR.\n\nPlease note that there might be duplicate entries. If there are, please remove them and add the duplicate emails to .mailmap directly to this PR."
+          branch: "actions/authors-update" # custom branch *just* for this Action.
+          commit-message: "meta: update AUTHORS"
+          author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
+          labels: meta

.github/workflows/find-inactive-collaborators.yml

@@ -28,3 +28,14 @@ jobs:
 
       - name: Find inactive collaborators
         run: tools/find-inactive-collaborators.mjs ${{ env.NUM_COMMITS }}
+
+      - name: Open pull request
+        uses: gr2m/create-or-update-pull-request-action@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
+          body: This PR was generated by tools/find-inactive-collaborators.yml.
+          commit-message: "meta: move one or more collaborators to emeritus"
+          labels: meta
+          title: "meta: move one or more collaborators to emeritus"

CHANGELOG.md

@@ -32,7 +32,8 @@ release.
 </tr>
 <tr>
     <td valign="top">
-<b><a href="doc/changelogs/CHANGELOG_V16.md#16.7.0">16.7.0</a></b><br/>
+<b><a href="doc/changelogs/CHANGELOG_V16.md#16.8.0">16.8.0</a></b><br/>
+<a href="doc/changelogs/CHANGELOG_V16.md#16.7.0">16.7.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V16.md#16.6.2">16.6.2</a><br/>
 <a href="doc/changelogs/CHANGELOG_V16.md#16.6.1">16.6.1</a><br/>
 <a href="doc/changelogs/CHANGELOG_V16.md#16.6.0">16.6.0</a><br/>

GOVERNANCE.md

@@ -15,15 +15,16 @@
 
 ## Triagers
 
-Triagers assess newly-opened issues in the nodejs/node and nodejs/help
-repositories. There is no GitHub team for triagers at the moment.
+Triagers assess newly-opened issues in the [nodejs/node][] and [nodejs/help][]
+repositories. The GitHub team for Node.js triagers is @nodejs/issue-triage.
+Triagers are given the "Triage" GitHub role and have:
 
-Triagers have:
-* ability to label issues
-* ability to comment, close, and reopen issues
+* Ability to label issues and pull requests
+* Ability to comment, close, and reopen issues and pull requests
 
 See:
 
+* [List of triagers](./README.md#triagers)
 * [A guide for triagers](./doc/guides/contributing/issues.md#triaging-a-bug-report)
 
 ## Collaborators
@@ -174,4 +175,5 @@ The TSC follows a [Consensus Seeking][] decision-making model per the
 [Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
 [TSC Charter]: https://github.com/nodejs/TSC/blob/HEAD/TSC-Charter.md
 [collaborators discussion page]: https://github.com/orgs/nodejs/teams/collaborators/discussions
+[nodejs/help]: https://github.com/nodejs/help
 [nodejs/node]: https://github.com/nodejs/node

Makefile

@@ -1235,7 +1235,7 @@ LINT_MD_TARGETS = doc src lib benchmark test tools/doc tools/icu $(wildcard *.md
 LINT_MD_FILES = $(shell $(FIND) $(LINT_MD_TARGETS) -type f \
 	! -path '*node_modules*' ! -path 'test/fixtures/*' -name '*.md' \
 	$(LINT_MD_NEWER))
-run-lint-md = tools/lint-md.js -q -f --no-stdout $(LINT_MD_FILES)
+run-lint-md = tools/lint-md.mjs -q -f --no-stdout $(LINT_MD_FILES)
 # Lint all changed markdown files maintained by us
 tools/.mdlintstamp: $(LINT_MD_FILES)
 	$(info Running Markdown linter...)

README.md

@@ -152,6 +152,8 @@ For information on reporting security vulnerabilities in Node.js, see
 For information about the governance of the Node.js project, see
 [GOVERNANCE.md](./GOVERNANCE.md).
 
+<!-- node-core-utils depends on the format of the TSC list. If the
+     format changes, those utilities need to be tested and updated. -->
 ### TSC (Technical Steering Committee)
 
 <!--lint disable prohibited-strings-->
@@ -249,6 +251,9 @@ For information about the governance of the Node.js project, see
 
 </details>
 
+<!-- node-core-utils and find-inactive-collaborators.mjs depend on the format
+     of the collaborator list. If the format changes, those utilities need to be
+     tested and updated. -->
 ### Collaborators
 
 * [addaleax](https://github.com/addaleax) -
@@ -462,6 +467,8 @@ For information about the governance of the Node.js project, see
 
 <summary>Emeriti</summary>
 
+<!-- find-inactive-collaborators.mjs depends on the format of the emeriti list.
+     If the format changes, those utilities need to be tested and updated. -->
 ### Collaborator emeriti
 
 * [andrasq](https://github.com/andrasq) -
@@ -613,6 +620,8 @@ maintaining the Node.js project.
 
 * [Ayase-252](https://github.com/Ayase-252) -
 **Qingyu Deng** &lt;i@ayase-lab.com&gt;
+* [himadriganguly](https://github.com/himadriganguly) -
+**Himadri Ganguly** &lt;himadri.tech@gmail.com&gt; (he/him)
 * [marsonya](https://github.com/marsonya) -
 **Akhil Marsonya** &lt;akhil.marsonya27@gmail.com&gt; (he/him)
 * [PoojaDurgad](https://github.com/PoojaDurgad) -

common.gypi

@@ -36,7 +36,7 @@
 
     # Reset this number to 0 on major V8 upgrades.
     # Increment by one for each non-official patch applied to deps/v8.
-    'v8_embedder_string': '-node.19',
+    'v8_embedder_string': '-node.20',
 
     ##### V8 defaults for Node.js #####
 

deps/npm/README.md

@@ -29,6 +29,7 @@ If you're looking to manage multiple versions of **`node`** &/or **`npm`**, cons
 * [**`volta`**](https://github.com/volta-cli/volta)
 * [**`nodenv`**](https://github.com/nodenv/nodenv)
 * [**`asdf-nodejs`**](https://github.com/asdf-vm/asdf-nodejs)
+* [**`nvm-windows`**](https://github.com/coreybutler/nvm-windows)
 
 ### Usage
 

deps/npm/docs/content/commands/npm-access.md

@@ -85,13 +85,17 @@ Management of teams and team memberships is done with the `npm team` command.
 
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
 <!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `otp`
 
 * Default: null
@@ -103,6 +107,9 @@ when publishing or changing package permissions with `npm access`.
 If not set, and a registry response fails with a challenge for a one-time
 password, npm will prompt on the command line for one.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
 
 ### See Also

deps/npm/docs/content/commands/npm-adduser.md

@@ -37,13 +37,17 @@ your existing record.
 
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
 <!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `scope`
 
 * Default: the scope of the current project, if any, or ""
@@ -74,6 +78,9 @@ npm init --scope=@foo --yes
 ```
 
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
 
 ### See Also

deps/npm/docs/content/commands/npm-audit.md

@@ -191,6 +191,7 @@ $ npm audit --audit-level=moderate
 
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
 <!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
 #### `audit-level`
 
 * Default: null
@@ -199,6 +200,9 @@ $ npm audit --audit-level=moderate
 The minimum level of vulnerability for `npm audit` to exit with a non-zero
 exit code.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `dry-run`
 
 * Default: false
@@ -212,6 +216,9 @@ commands that modify your local installation, eg, `install`, `update`,
 Note: This is NOT honored by other network related commands, eg `dist-tags`,
 `owner`, etc.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `force`
 
 * Default: false
@@ -237,6 +244,9 @@ mistakes, unnecessary performance degradation, and malicious input.
 If you don't have a clear idea of what you want to do, it is strongly
 recommended that you do not use this option!
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `json`
 
 * Default: false
@@ -249,6 +259,9 @@ Whether or not to output JSON data, rather than the normal output.
 
 Not supported by all npm commands.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `package-lock-only`
 
 * Default: false
@@ -263,6 +276,9 @@ instead of checking `node_modules` and downloading dependencies.
 For `list` this means the output will be based on the tree described by the
 `package-lock.json`, rather than the contents of `node_modules`.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `omit`
 
 * Default: 'dev' if the `NODE_ENV` environment variable is set to
@@ -281,6 +297,9 @@ it will be included.
 If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment
 variable will be set to `'production'` for all lifecycle scripts.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `workspace`
 
 * Default:
@@ -303,6 +322,9 @@ brand new workspace within the project.
 
 This value is not exported to the environment for child processes.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `workspaces`
 
 * Default: false
@@ -313,6 +335,9 @@ workspaces.
 
 This value is not exported to the environment for child processes.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
 
 ### See Also

deps/npm/docs/content/commands/npm-bin.md

@@ -20,6 +20,7 @@ Print the folder where npm will install executables.
 
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
 <!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
 #### `global`
 
 * Default: false
@@ -34,6 +35,9 @@ folder instead of the current working directory. See
 * bin files are linked to `{prefix}/bin`
 * man pages are linked to `{prefix}/share/man`
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
 
 ### See Also

deps/npm/docs/content/commands/npm-bugs.md

@@ -23,6 +23,7 @@ will search for a `package.json` in the current folder and use the `name` proper
 
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
 <!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
 #### `browser`
 
 * Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"`
@@ -35,13 +36,19 @@ terminal.
 
 Set to `true` to use default system URL opener.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 #### `registry`
 
 * Default: "https://registry.npmjs.org/"
 * Type: URL
 
 The base URL of the npm registry.
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
 
 ### See Also

deps/npm/docs/content/commands/npm-cache.md

@@ -77,6 +77,7 @@ verify`.
 
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
 <!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
 #### `cache`
 
 * Default: Windows: `%LocalAppData%\npm-cache`, Posix: `~/.npm`
@@ -85,6 +86,9 @@ verify`.
 The location of npm's cache directory. See [`npm
 cache`](/commands/npm-cache)
 
+<!-- automatically generated, do not edit manually -->
+<!-- see lib/utils/config/definitions.js -->
+
 <!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
 
 ### See Also