Try wrap up PR

.github/workflows/release.yml

@@ -3,15 +3,9 @@ name: Release executable files for macOS
 on:
   workflow_dispatch:
     inputs:
-      version_digit:
-        description: 'Version digit (major | minor | patch)'
+      version:
+        description: "Version to deploy assets for"
         required: true
-        default: 'patch'
-        type: choice
-        options:
-        - major
-        - minor
-        - patch
 
 jobs:
   release:
@@ -31,26 +25,32 @@ jobs:
 
       - name: Check out repository code
         uses: actions/checkout@v3
-      
+
       - name: Use node
         uses: actions/setup-node@v3
         with:
           node-version: "14"
 
       - name: Install dependencies
         run: npm install
-      
+
       - name: Build
         run: npm run build
 
+      - name: Tell release-it to do the GitHub release here
+        run:
+          node -e 'const fs = require("fs"); const a = JSON.parse(fs.readFileSync("./.release-it.json", "utf8"));
+          a.github.release = true; a.hooks["after:bump"] = a.hooks["_after:bump"]; a.hooks["after:release"] =
+          a.hooks["_after:release"]; fs.writeFileSync("./.release-it.json", JSON.stringify(a))'
+
       - name: Package
         run: |
           git config --global user.email "action@github.com"
           git config --global user.name "GitHub Action"
-          npm run release -- ${{ github.event.inputs.version_digit }} --ci
+          npm run release -- ${{ github.event.inputs.version }} --no-npm --ci
 
       - name: Update homebrew/tap repo for new release
         shell: bash
         run: scripts/create-homebrew-tap-pr.sh
         env:
-          VERSION: ${{ env.VERSION }}
+          VERSION: ${{ env.VERSION }}

.release-it.json

@@ -1,12 +1,12 @@
 {
-  "github": {
-    "release": true,
-    "assets": "brew-distribution/*.zip"
-  },
+  "_": "CI will switch the release here to true",
+  "github": { "release": false, "assets": "brew-distribution/*.zip" },
   "buildCommand": "yarn package:x64; yarn package:arm64",
   "hooks": {
     "before:bump": "yarn declarations; yarn build:schemas",
-    "after:bump": "yarn package:x64; yarn package:arm64",
-    "after:release": "export VERSION=${version}; echo 'VERSION=${version}' >> $GITHUB_ENV"
+    "after:release": "gh workflow run .github/workflows/release.yml version=${version}",
+    "_": "CI will remove the _ from both of the below lines",
+    "_after:bump": "yarn package:x64; yarn package:arm64",
+    "_after:release": "export VERSION=${version}; echo 'VERSION=${version}' >> $GITHUB_ENV"
   }
 }

CHANGELOG.md

@@ -16,11 +16,16 @@
 
 <!-- Your comment below this -->
 
-- Support arm64 binary generation for Apple silicon users [#1342](https://github.com/danger/danger-js/pull/1342) [@pepix]
 
 <!-- Your comment above this -->
 
-## 11.1.2
+
+## 11.2.1
+
+- Updates jsonwebtoken due to security issues
+- Support arm64 binary generation for Apple silicon users [#1342](https://github.com/danger/danger-js/pull/1342) [@pepix]
+
+## 11.2.1
 
 - Bug fix for bitbucket bot detection ignoring case #1291
 

README.md

@@ -99,8 +99,9 @@ Check the issues, I try and keep my short term perspective there. Long term is i
 Following [this commit](https://github.com/danger/danger-js/commit/a26ac3b3bd4f002acd37f6a363c8e74c9d5039ab) as a model:
 
 - Checkout the `main` branch. Ensure your working tree is clean, and make sure you have the latest changes by running
-  `git pull`.
+  `git pull; yarn`.
 - Publish - `npm run release -- patch --ci`.
+- This will trigger a CI run which updates homebrew for the native builds
 
 :ship:
 

VISION.md

@@ -26,7 +26,7 @@ JS has been accomplished:
 
 So, what now? Well. It's kinda done and now can mature. For the past few years Danger Ruby has solidified and become
 foundational infrastructure which you can trust won't change much, now Danger JS can be in the same place. This is a
-great place to be a developer tool.
+great place to be for a developer tool.
 
 # Why Danger JS? What about Danger Ruby?