From 6b001fd48249c2f4848f157d8290dc1ae84871a0 Mon Sep 17 00:00:00 2001 From: Jeremy Green Date: Wed, 29 Nov 2023 12:16:17 -0800 Subject: [PATCH] [Release process] Use a PAT to generate the upgrade PR (#1212) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit In order to get the CI workflow to run after we create the upgrade PR we need to create the PR using a PAT. (Weird GitHub Actions rules... 🤷) --- .github/workflows/version-bump.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/version-bump.yml b/.github/workflows/version-bump.yml index 20a17f524..5f41180fd 100644 --- a/.github/workflows/version-bump.yml +++ b/.github/workflows/version-bump.yml @@ -50,6 +50,7 @@ jobs: delete-branch: true title: "BT-Core version bump: ${{ inputs.versionBump }} - ${{ steps.bump-core.outputs.NEW_VERSION_NUMBER }}" add-paths: "Gemfile, Gemfile.lock, package.json, yarn.lock" + token: ${{ secrets.UPGRADE_PR_PAT }} body: | Version bump of the `core` ruby gems and npm packages to version `${{ steps.bump-core.outputs.NEW_VERSION_NUMBER }}`