Improve docs of release workflow

Author: adamkudrna

.github/workflows/pr-labeler.yml

@@ -8,6 +8,6 @@ jobs:
   pr-labeler:
     runs-on: ubuntu-18.04
     steps:
-      - uses: TimonVS/pr-labeler-action@v3
+      - uses: TimonVS/pr-labeler-action@v3.1.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release-management.yml

@@ -41,7 +41,7 @@ jobs:
 
       - name: Check package.json for version change
         id: check_package_version
-        uses: EndBug/version-check@v1
+        uses: EndBug/version-check@v1.6.0
 
       - name: Log when version changed
         if: steps.check_package_version.outputs.changed == 'true'
@@ -63,7 +63,7 @@ jobs:
     runs-on: ubuntu-18.04
     steps:
       - name: Draft release on GitHub
-        uses: release-drafter/release-drafter@v5
+        uses: release-drafter/release-drafter@v5.12.1
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
@@ -80,7 +80,7 @@ jobs:
       # `build_and_test` job first so this job is skipped rather than exited with an error.
       - name: Publish matching GitHub release draft
         id: github_release
-        uses: JamesMGreene/node-draft-releaser@v1
+        uses: JamesMGreene/node-draft-releaser@v1.1.2
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
@@ -139,7 +139,7 @@ jobs:
           name: docs
 
       - name: Deploy docs to GitHub Pages
-        uses: JamesIves/github-pages-deploy-action@3.6.2
+        uses: JamesIves/github-pages-deploy-action@3.7.1
         with:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           FOLDER: docs # Must match the name of the artifact used.

RELEASING.md

@@ -53,8 +53,9 @@ See the source of `.github/workflows` for details.
       overwritten. Save your changes in release draft with the _Save draft_
       button, **do not publish** yet!
 
-   3. Get back to the repository, commit both files as `Bump version` in
-      `release/<VERSION_NUMBER>` branch, create a pull request, and merge it.
+   3. Get back to the repository, commit both files as
+      `Bump version to <VERSION_NUMBER>` in `release/<VERSION_NUMBER>` branch,
+      create a pull request, hold your breath, and—merge it.
 
 3. **Automatic:** once the release pull request from step 2.3 is merged, the
    following actions are triggered automatically:
@@ -64,3 +65,6 @@ See the source of `.github/workflows` for details.
    2. Git tag with the version number from step 2 is added to `master` branch.
    3. Package is built and published to npm package registry.
    4. Documentation is built and deployed to production.
+
+**Note:** prefix version number with `v` everywhere except in `package.json` and
+`package-lock.json`.