Migrate CI from Travis and AppVeyor to Github actions

.github/workflows/pr.yml

@@ -0,0 +1,39 @@
+# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+
+name: Pull Requests
+
+on: [pull_request]
+
+jobs:
+  build:
+    strategy:
+      fail-fast: false
+      matrix:
+        node: [18.16.1]
+        os: [windows-2019, ubuntu-20.04, macos-11]
+
+    runs-on: ${{ matrix.os }}
+    steps:
+      - name: Cancel Previous Runs
+        uses: styfle/cancel-workflow-action@0.11.0
+        with:
+          access_token: ${{ github.token }}
+      - uses: actions/checkout@v3
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+      - name: Use Node.js ${{ matrix.node }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node }}
+      - name: Add msbuild to PATH
+        # we need msbuild tools for the `bcrypto` module
+        if: startsWith(matrix.os, 'windows-')
+        uses: microsoft/setup-msbuild@v1.1
+      - uses: de-vri-es/setup-git-credentials@v2
+        with:
+          credentials: ${{secrets.PAT}}
+      - run: npm ci
+      - run: npm run test
+        env:
+          FORCE_COLOR: 1

.github/workflows/release.yml

@@ -0,0 +1,91 @@
+name: Release
+
+# this should only run on release, but I'm triggering on pull_request so that I can test it
+on: [pull_request]
+
+jobs:
+  build:
+    strategy:
+      fail-fast: false
+      matrix:
+        node: [18.16.1]
+        os: [windows-2019, ubuntu-20.04, macos-12]
+
+    runs-on: ${{ matrix.os }}
+    steps:
+      - name: Cancel Previous Runs
+        uses: styfle/cancel-workflow-action@0.11.0
+        with:
+          access_token: ${{ github.token }}
+      - uses: actions/checkout@v3
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+      - name: Use Node.js ${{ matrix.node }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node }}
+      - name: Downgrade npm to 8.16.0 # see https://github.com/electron-userland/electron-builder/issues/7755#issuecomment-1744147677
+        if: startsWith(matrix.os, 'macos-')
+        run: npm install -g npm@8.16.0
+      - name: Add msbuild to PATH
+        # we need msbuild tools for the `bcrypto` module
+        if: startsWith(matrix.os, 'windows-')
+        uses: microsoft/setup-msbuild@v1.1
+      - uses: de-vri-es/setup-git-credentials@v2
+        with:
+          credentials: ${{secrets.PAT}}
+      - if: startsWith(matrix.os, 'windows-')
+        run: |
+          $bytes = [Convert]::FromBase64String('${{ secrets.WINDOWS_CODE_SIGNING_PFX_BASE_64 }}');
+          Add-Content -Path '.\cert.pfx' -Value $bytes -AsByteStream;
+          Import-PfxCertificate -Password (ConvertTo-SecureString '${{ secrets.WINDOWS_CODE_SIGNING_PFX_PASSWORD }}' -AsPlainText -Force) -FilePath .\cert.pfx -CertStoreLocation Cert:\CurrentUser\My > $null;
+      - run: npm ci
+        env:
+          FORCE_COLOR: 1
+      - name: Build for Linux
+        if: startsWith(matrix.os, 'ubuntu-')
+        run: npm run build-linux
+        env:
+          GH_TOKEN: ${{ secrets.GH_TOKEN }}
+          PUBLISH_FOR_PULL_REQUEST: true
+      - name: Build for Windows
+        if: startsWith(matrix.os, 'windows-')
+        run: npm run build-windows;
+        env:
+          GH_TOKEN: ${{ secrets.GH_TOKEN }}
+          CSC_FOR_PULL_REQUEST: true
+          PUBLISH_FOR_PULL_REQUEST: true
+      - name: Build for Mac
+        if: startsWith(matrix.os, 'macos-')
+        run: |
+          echo "Configuring keychain..."
+          export CERT=osx.p12
+          export NOTARIZE=true
+          base64 -d <<< "${{ secrets.APPLE_CERTIFICATE_P12_BASE64 }}" > $CERT
+          export CSC_KEYCHAIN=build.keychain
+          export KEYCHAIN_PASS=$RANDOM.$RANDOM.$RANDOM
+          security create-keychain -p $KEYCHAIN_PASS $CSC_KEYCHAIN
+          security default-keychain -s $CSC_KEYCHAIN
+          security unlock-keychain -p $KEYCHAIN_PASS $CSC_KEYCHAIN
+          security import $CERT -k $CSC_KEYCHAIN -P "${{ secrets.APPLE_CERTIFICATE_P12_PASSWORD }}" -T /usr/bin/codesign
+          security set-keychain-settings $CSC_KEYCHAIN
+          echo "Setting key partition list"
+          security set-key-partition-list -S "apple-tool:,apple:,codesign:" -s -k $KEYCHAIN_PASS $CSC_KEYCHAIN >/dev/null 2>&1
+          export DEBUG=electron-notarize:*
+          npm run build-mac
+        env:
+          GH_TOKEN: ${{ secrets.GH_TOKEN }}
+          PUBLISH_FOR_PULL_REQUEST: true
+          CSC_FOR_PULL_REQUEST: true
+          APPLE_ID: ${{ secrets.APPLEID }}
+          APPLE_APP_SPECIFIC_PASSWORD: ${{ secrets.APPLEIDPASSWORD }}
+      - uses: actions/upload-artifact@v3
+        with:
+          name: Release
+          path: |
+            dist/*.AppImage
+            dist/*.dmg
+            dist/*.blockmap
+            dist/*.zip
+            dist/*.appx
+            dist/*.yml

.gitignore

@@ -1,4 +1,3 @@
-certs/cert.pfx
 dist
 node_modules
 .DS_Store

.nvmrc

@@ -1 +1 @@
-14.21.1
+18.16.1

README.md

@@ -27,8 +27,8 @@ Requirements:
 To get started:
 
 0. Clone this repo
-0. Run `npm install`
-0. Run `npm run dev`
+1. Run `npm install`
+2. Run `npm run dev`
 
 If using Windows, you may need [windows-build-tools](https://www.npmjs.com/package/windows-build-tools) installed first.
 
@@ -40,15 +40,15 @@ Each platform has an associated `npm run` configuration to help you build on eac
 
 Building on Windows will create a `.appx` file for use with the Windows Store.
 
-Before building, create the `./certs` directory with the following files:
+Before building, create the following files:
 
-* `./certs/cert.pfx` - Note a `.pfx` file is identical to a `.p12`. (Just change the extension if you've been given a `.p12`.)
+- `./cert.pfx` - Note a `.pfx` file is identical to a `.p12`. (Just change the extension if you've been given a `.p12`.)
 
 In order to build on Windows, you must first ensure you have the [Windows 10 SDK](https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk) installed. If you have errors during the build process, ensure the package.json file's `windowsStoreConfig.windowsKit` points to your Windows 10 SDK directory. The one specified in the package.json file currently is what worked at the time this process was figured out; it may need to be updated periodically.
 
 Because Windows requires a certificate to build the package -- and that certificate requires a password -- you'll need to run the following command instead of `npm run make`:
 
-In order to successfully sign the appx bundle on Windows 10, an alternative `signtool.exe` to the binary bundled with electron-builder may need to be used. See https://github.com/electron-userland/electron-builder/pull/6817. 
+In order to successfully sign the appx bundle on Windows 10, an alternative `signtool.exe` to the binary bundled with electron-builder may need to be used. See https://github.com/electron-userland/electron-builder/pull/6817.
 
 Install Windows SDK 18362 from https://developer.microsoft.com/en-us/windows/downloads/sdk-archive, and set the signtool path for electron-builder as follows:
 
@@ -96,10 +96,10 @@ Asset generation generally only needs to happen once, or whenever the app's logo
 
 Two tools were used:
 
-* [electron-icon-maker](https://www.npmjs.com/package/electron-icon-maker)
-* [svg2uwptiles](https://www.npmjs.com/package/svg2uwptiles)
+- [electron-icon-maker](https://www.npmjs.com/package/electron-icon-maker)
+- [svg2uwptiles](https://www.npmjs.com/package/svg2uwptiles)
 
-`electron-icon-maker` generates assets for all platforms when using Electron's `squirrel` package, and these assets live in `./static/icons`. `svg2uwptiles` generates all assets needed for the Windows appx build, and those assets live in `./build/appx`. These locations *can* be changed in the future, but make sure to change the associated configuration pointing to these assets.
+`electron-icon-maker` generates assets for all platforms when using Electron's `squirrel` package, and these assets live in `./static/icons`. `svg2uwptiles` generates all assets needed for the Windows appx build, and those assets live in `./build/appx`. These locations _can_ be changed in the future, but make sure to change the associated configuration pointing to these assets.
 
 Note from the author: I found managing these assets manually -- especially the appx assets -- was a pain. If possible, try not to edit the assets themselves and use one of the generators above.
 
@@ -115,7 +115,7 @@ When "extras" change they should be uploaded to a new release, and a correspondi
 
 Below is a `.vscode/launch.json` configuration that will attach to both the **main** and **renderer** processes. You only need to run the **Launch Ganache UI** configuration; the renderer attach configuration will run automatically.
 
-``` jsonc
+```jsonc
 {
   "version": "0.2.0",
   "configurations": [
@@ -148,7 +148,6 @@ Below is a `.vscode/launch.json` configuration that will attach to both the **ma
 }
 ```
 
-
 ### By Truffle
 
 Ganache is part of the Truffle suite of tools. [Find out more!](https://trufflesuite.com)