v17.2.0 release proposal

.github/ISSUE_TEMPLATE/2-feature-request.md

@@ -1,7 +1,7 @@
 ---
 name: "\U0001F680 Feature request"
 about: Suggest an idea for this project
-
+labels: feature request
 ---
 
 <!--

.github/workflows/commit-lint.yml

@@ -1,4 +1,4 @@
-name: "Commit messages adheres to guidelines at https://goo.gl/p2fr5Q"
+name: "First commit message adheres to guidelines at https://goo.gl/p2fr5Q"
 
 on: [pull_request]
 
@@ -11,15 +11,18 @@ jobs:
     steps:
       - name: Compute number of commits in the PR
         id: nb-of-commits
-        run: echo "::set-output name=nb::$((${{ github.event.pull_request.commits }} + 1))"
+        run: |
+          echo "::set-output name=plusOne::$((${{ github.event.pull_request.commits }} + 1))"
+          echo "::set-output name=minusOne::$((${{ github.event.pull_request.commits }} - 1))"
       - uses: actions/checkout@v2
         with:
-          fetch-depth: ${{ steps.nb-of-commits.outputs.nb }}
+          fetch-depth: ${{ steps.nb-of-commits.outputs.plusOne }}
+      - run: git reset HEAD^2
       - name: Install Node.js
         uses: actions/setup-node@v2
         with:
           node-version: ${{ env.NODE_VERSION }}
-      - name: Validate commit messages
+      - name: Validate commit message
         run: |
           echo "::add-matcher::.github/workflows/commit-lint-problem-matcher.json"
-          git log --oneline -${{ github.event.pull_request.commits }} HEAD^ | awk '{ if ($2 != "fixup!" && $2 != "squash!") { print $1 } }' | xargs npx -q core-validate-commit --no-validate-metadata --tap
+          git rev-parse HEAD~${{ steps.nb-of-commits.outputs.minusOne }} | xargs npx -q core-validate-commit --no-validate-metadata --tap

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

@@ -2,13 +2,13 @@ name: Find inactive collaborators
 
 on:
   schedule:
-    # Run on the 15th day of the month at 4:05 AM UTC.
-    - cron: '5 4 15 * *'
+    # Run every Monday at 4:05 AM UTC.
+    - cron: '5 4 * * 1'
 
   workflow_dispatch:
 
 env:
-  NODE_VERSION: 16.x
+  NODE_VERSION: lts/*
   NUM_COMMITS: 5000
 
 jobs:

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

@@ -0,0 +1,52 @@
+name: Find inactive TSC members
+
+on:
+  schedule:
+    # Run every Tuesday 12:05 AM UTC.
+    - cron: '5 0 * * 2'
+
+  workflow_dispatch:
+
+env:
+  NODE_VERSION: lts/*
+
+jobs:
+  find:
+    if: github.repository == 'nodejs/node'
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout the repo
+        uses: actions/checkout@v2
+
+      - name: Clone nodejs/TSC repository
+        uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+          repository: nodejs/TSC
+          path: .tmp
+
+      - name: Use Node.js ${{ env.NODE_VERSION }}
+        uses: actions/setup-node@v2
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+
+      - name: Find inactive TSC members
+        run: tools/find-inactive-tsc.mjs >> $GITHUB_ENV
+
+      - name: Open pull request
+        uses: gr2m/create-or-update-pull-request-action@v1
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_USER_TOKEN }}
+        with:
+          author: Node.js GitHub Bot <github-bot@iojs.org>
+          branch: actions/inactive-tsc
+          body: |
+            This PR was generated by tools/find-inactive-tsc.yml.
+
+            @nodejs/tsc ${{ env.INACTIVE_TSC_HANDLES }}
+
+            ${{ env.DETAILS_FOR_COMMIT_BODY }}
+          commit-message: "meta: move one or more TSC members to emeritus"
+          labels: meta
+          title: "meta: move one or more TSC members to emeritus"

.github/workflows/tools.yml

@@ -0,0 +1,63 @@
+name: "tools update"
+on:
+  schedule:
+    # Run once a week at 00:05 AM UTC on Saturday.
+    - cron: '5 0 * * 6'
+
+  workflow_dispatch:
+
+jobs:
+  tools_update:
+    if: github.repository == 'nodejs/node'
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false  # Prevent other jobs from aborting if one fails
+      matrix:
+        include:
+          - id: eslint
+            run: |
+              cd tools
+              NEW_VERSION=$(npm view eslint dist-tags.latest)
+              CURRENT_VERSION=$(node -p "require('./node_modules/eslint/package.json').version")
+              if [ "$NEW_VERSION" != "$CURRENT_VERSION" ]; then
+                echo "NEW_VERSION=$NEW_VERSION" >> $GITHUB_ENV
+                ./update-eslint.sh
+              fi
+          - id: "@babel/eslint-parser"
+            run: |
+              cd tools
+              NEW_VERSION=$(npm view @babel/eslint-parser dist-tags.latest)
+              CURRENT_VERSION=$(node -p "require('./node_modules/@babel/eslint-parser/package.json').version")
+              if [ "$NEW_VERSION" != "$CURRENT_VERSION" ]; then
+                echo "NEW_VERSION=$NEW_VERSION" >> $GITHUB_ENV
+                ./update-babel-eslint.sh
+              fi
+          - id: "lint-md-dependencies"
+            run: |
+              cd tools/lint-md
+              npm ci
+              NEW_VERSION=$(npm outdated --parseable | cut -d: -f4 | xargs)
+              if [ "$NEW_VERSION" != "" ]; then
+                echo "NEW_VERSION=$NEW_VERSION" >> $GITHUB_ENV
+                rm -rf package-lock.json node_modules
+                # Include $NEW_VERSION to explicitly update the package.json
+                # entry for the dependency and also so that semver-major updates
+                # are not skipped.
+                npm install --ignore-scripts $NEW_VERSION
+                npm install --ignore-scripts
+                cd ../..
+                make lint-md-rollup
+              fi
+    steps:
+      - uses: actions/checkout@v2
+      - run: ${{ matrix.run }}
+      - uses: gr2m/create-or-update-pull-request-action@v1  # Create a PR or update the Action's existing PR
+        env:
+          GITHUB_TOKEN: ${{ secrets.GH_USER_TOKEN }}
+        with:
+          author: Node.js GitHub Bot <github-bot@iojs.org>
+          body: "This is an automated update of ${{ matrix.id }} to ${{ env.NEW_VERSION }}."
+          branch: "actions/tools-update-${{ matrix.id }}"  # Custom branch *just* for this Action.
+          commit-message: "tools: update ${{ matrix.id }} to ${{ env.NEW_VERSION }}"
+          labels: tools
+          title: "tools: update ${{ matrix.id }} to ${{ env.NEW_VERSION }}"

.mailmap

@@ -1,3 +1,4 @@
+3nprob <git@3n.anonaddy.com> <3nprob@3nprob>
 Aaron Bieber <aaron@bolddaemon.com> <deftly@gmail.com>
 Aaron Heckmann <aaron.heckmann@gmail.com> <aaron.heckmann+github@gmail.com>
 Aayush Ahuja <aayush.a@directi.com>
@@ -340,6 +341,8 @@ Miroslav Bajtoš <oss@bajtos.net> <miro.bajtos@gmail.com>
 Miroslav Bajtoš <oss@bajtos.net> <miroslav@strongloop.com>
 Mitar Milutinovic <mitar.git@tnode.com>
 Mithun Sasidharan <mithunsasidharan89@gmail.com> <msasidharan@paypal.com>
+Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
+Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com> <62040526+VoltrexMaster@users.noreply.github.com>
 Myles Borins <myles.borins@gmail.com> <mborins@us.ibm.com>
 Myles Borins <myles.borins@gmail.com> <mylesborins@github.com>
 Myles Borins <myles.borins@gmail.com> <mylesborins@google.com>
@@ -430,6 +433,7 @@ Shiya Luo <luo.shiya@gmail.com>
 Shobhit Chittora <chittorashobhit@gmail.com> <schittora@paypal.com>
 Siddharth Mahendraker <siddharth_mahen@hotmail.com> <siddharth_mahen@me.com>
 Simon Willison <simon@simonwillison.net>
+Simone Busoli <simone.busoli@nearform.com> <simone.busoli@gmail.com>
 Siobhan O'Donovan <siobhan@justshiv.com>
 Siyuan Gao <siyuangao@gmail.com>
 solebox <solekiller@gmail.com> <5013box@gmail.com>
@@ -498,10 +502,10 @@ Tyler Larson <talltyler@gmail.com>
 Ujjwal Sharma <ryzokuken@disroot.org> <ryzokuken@igalia.com>
 Ujjwal Sharma <ryzokuken@disroot.org> <usharma1998@gmail.com>
 Uttam Pawar <upawar@gmail.com> <uttam.c.pawar@intel.com>
+Viero Fernando <vierofernando9@gmail.com> <60427892+vierofernando@users.noreply.github.com>
 Viktor Karpov <viktor.s.karpov@gmail.com>
 Vincent Voyer <v@fasterize.com>
 Vladimir de Turckheim <vlad2t@hotmail.com>
-Voltrex <mohammadkeyvanzade94@gmail.com> <62040526+VoltrexMaster@users.noreply.github.com>
 vsemozhetbyt <vsemozhetbyt@gmail.com>
 Vyacheslav Egorov <vegorov@chromium.org>
 Wang Xinyong <wang.xy.chn@gmail.com> <wangxy.chn@gmail.com>

AUTHORS

@@ -3249,7 +3249,7 @@ Darkripper214 <phakorn214@gmail.com>
 Anu Pasumarthy <anupama.pasumarthy@gmail.com>
 HiroyukiYagihashi <hey@hiroy.uk>
 Arkerone <shaita.axel@gmail.com>
-Voltrex <mohammadkeyvanzade94@gmail.com>
+Mohammed Keyvanzadeh <mohammadkeyvanzade94@gmail.com>
 ycjcl868 <45808948@qq.com>
 Serkan Özel <serkanozel380@gmail.com>
 Ferdi <iguessitsokaythen@gmail.com>
@@ -3324,7 +3324,7 @@ Node.js GitHub Bot <github-bot@iojs.org>
 Alexey Ten <alexeyten@gmail.com>
 JckXia <ys3xia@uwaterloo.ca>
 Christian Boehlke <christian@boehlkes.de>
-null <60427892+vierofernando@users.noreply.github.com>
+Viero Fernando <vierofernando9@gmail.com>
 Dominic Elm <elmdominic@gmx.net>
 treysis <treysis@gmx.net>
 shfshanyue <xianger94@gmail.com>
@@ -3360,5 +3360,15 @@ simon-id <simon.id@protonmail.com>
 Francesco Trotta <github@fasttime.org>
 Richie Bendall <richiebendall@gmail.com>
 ryan <chai_xb@163.com>
+Piotr Rybak <rybak.piotr@yahoo.com>
+Jean Burellier <sheplu@users.noreply.github.com>
+Subhi Al Hasan <subhialhasan@protonmail.com>
+3nprob <git@3n.anonaddy.com>
+Martin Jansa <martin.jansa@lge.com>
+Omar El-Mihilmy <mihilmy@yahoo.com>
+Yoshiki <yosyos0306@gmail.com>
+Keeley Hammond <vertedinde@electronjs.org>
+git-srinivas <vykuntamsrinivas@gmail.com>
+Idan Attias <idana@wix.com>
 
 # Generated by tools/update-authors.js

BUILDING.md

@@ -143,8 +143,8 @@ platforms. This is true regardless of entries in the table below.
     community will only address issues that reproduce on native GNU/Linux
     systems. Issues that only reproduce on WSL should be reported in the
     [WSL issue tracker](https://github.com/Microsoft/WSL/issues). Running the
-    Windows binary (`node.exe`) in WSL is not recommended. It will not work
-    without workarounds such as stdio redirection.
+    Windows binary (`node.exe`) in WSL will not work without workarounds such as
+    stdio redirection.
 
 [^6]: Running Node.js on x86 Windows should work and binaries
     are provided. However, tests in our infrastructure only run on WoW64.
@@ -306,8 +306,7 @@ $ make test-only
 
 At this point, you are ready to make code changes and re-run the tests.
 
-If you are running tests before submitting a pull request, the recommended
-command is:
+If you are running tests before submitting a pull request, use:
 
 ```console
 $ make -j4 test
@@ -316,31 +315,34 @@ $ make -j4 test
 `make -j4 test` does a full check on the codebase, including running linters and
 documentation tests.
 
-Make sure the linter does not report any issues and that all tests pass. Please
-do not submit patches that fail either check.
-
-If you want to run the linter without running tests, use
+To run the linter without running tests, use
 `make lint`/`vcbuild lint`. It will lint JavaScript, C++, and Markdown files.
 
 If you are updating tests and want to run tests in a single test file
 (e.g. `test/parallel/test-stream2-transform.js`):
 
 ```text
-$ python tools/test.py test/parallel/test-stream2-transform.js
+$ tools/test.py test/parallel/test-stream2-transform.js
 ```
 
 You can execute the entire suite of tests for a given subsystem
 by providing the name of a subsystem:
 
 ```text
-$ python tools/test.py -J --mode=release child-process
+$ tools/test.py -J child-process
+```
+
+You can also execute the tests in a tests directory (such as `test/message`):
+
+```text
+$ tools/test.py -J test/message
 ```
 
 If you want to check the other options, please refer to the help by using
 the `--help` option:
 
 ```text
-$ python tools/test.py --help
+$ tools/test.py --help
 ```
 
 You can usually run tests directly with node:
@@ -355,7 +357,7 @@ the `lib` or `src` directories.
 The tests attempt to detect support for IPv6 and exclude IPv6 tests if
 appropriate. If your main interface has IPv6 addresses, then your
 loopback interface must also have '::1' enabled. For some default installations
-on Ubuntu that does not seem to be the case. To enable '::1' on the
+on Ubuntu, that does not seem to be the case. To enable '::1' on the
 loopback interface on Ubuntu:
 
 ```bash
@@ -364,7 +366,7 @@ sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=0
 
 You can use
 [node-code-ide-configs](https://github.com/nodejs/node-code-ide-configs)
-to run/debug tests, if your IDE configs are present.
+to run/debug tests if your IDE configs are present.
 
 #### Running coverage
 
@@ -392,7 +394,7 @@ If you are updating tests and want to collect coverage for a single test file
 
 ```text
 $ make coverage-clean
-$ NODE_V8_COVERAGE=coverage/tmp python tools/test.py test/parallel/test-stream2-transform.js
+$ NODE_V8_COVERAGE=coverage/tmp tools/test.py test/parallel/test-stream2-transform.js
 $ make coverage-report-js
 ```
 
@@ -401,7 +403,7 @@ by providing the name of a subsystem:
 
 ```text
 $ make coverage-clean
-$ NODE_V8_COVERAGE=coverage/tmp python tools/test.py -J --mode=release child-process
+$ NODE_V8_COVERAGE=coverage/tmp tools/test.py -J --mode=release child-process
 $ make coverage-report-js
 ```
 

CHANGELOG.md

@@ -33,7 +33,8 @@ release.
 </tr>
 <tr>
   <td valign="top">
-<b><a href="doc/changelogs/CHANGELOG_V17.md#17.1.0">17.1.0</a></b><br/>
+<b><a href="doc/changelogs/CHANGELOG_V17.md#17.2.0">17.2.0</a></b><br/>
+<a href="doc/changelogs/CHANGELOG_V17.md#17.1.0">17.1.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V17.md#17.0.1">17.0.1</a><br/>
 <a href="doc/changelogs/CHANGELOG_V17.md#17.0.0">17.0.0</a><br/>
     </td>

GOVERNANCE.md

@@ -64,7 +64,7 @@ See:
 * Participation in working groups
 * Merging pull requests
 
-The TSC can remove inactive collaborators or provide them with _Emeritus_
+The TSC can remove inactive collaborators or provide them with _emeritus_
 status. Emeriti may request that the TSC restore them to active status.
 
 ## Technical Steering Committee
@@ -87,9 +87,8 @@ Charter need approval by the OpenJS Foundation Cross-Project Council (CPC).
 
 ### TSC meetings
 
-The TSC meets in a voice conference call. Each year, the TSC elects a chair to
-run the meetings. The TSC streams its meetings for public viewing on YouTube or
-a similar service.
+The TSC meets in a video conference call. Each year, the TSC elects a chair to
+run the meetings. The TSC streams its meetings for public viewing on YouTube.
 
 The TSC agenda includes issues that are at an impasse. The intention of the
 agenda is not to review or approve all patches. Collaborators review and approve