refactor: use vVERSION branch name instead of release

Author: jsjoeio

.github/workflows/npm-brew.yaml

@@ -23,11 +23,15 @@ jobs:
     steps:
       - uses: actions/checkout@v3
 
+      - name: Get version branch
+        id: version-branch
+        run: echo "::set-output name=name::v$(jq .version package.json)"
+
       - name: Download artifact
         uses: dawidd6/action-download-artifact@v2
         id: download
         with:
-          branch: release
+          branch: v${{ steps.version-branch.outputs.name }}
           workflow_conclusion: completed
           name: "npm-package"
           path: release-npm-package

docs/MAINTAINING.md

@@ -164,7 +164,7 @@ If you're the current release manager, follow these steps:
 
 ### Publishing a release
 
-1. Create a new branch called `release` (the npm workflow will look for this when a new GitHub release is published)
+1. Create a new branch called `v0.0.0` (replace 0s with actual version aka v4.1.0)
 1. Run `yarn release:prep` and type in the new version (e.g., `3.8.1`)
 1. GitHub Actions will generate the `npm-package`, `release-packages` and
    `release-images` artifacts. You do not have to wait for this step to complete