From a8ee33b53381c1e3e530bbb939d4c0eb77f468a5 Mon Sep 17 00:00:00 2001 From: Daniel Lockyer Date: Mon, 12 Jul 2021 13:05:39 +0100 Subject: [PATCH] Updated CI release workflow to use built-in token no issue - `RELEASE_TOKEN` is currently a GitHub personal token, but this has some downsides: - if the token ever expires and I'm unaware, it'll break the release process - GitHub Releases say the creator was `daniellockyer` even if someone else actually did the release - this commit switches over to using the built-in `GITHUB_TOKEN`, which is owned by the `github-actions` app and should never expire - aside from that, Ghost releases will be created by the neutral `github-actions` account --- .github/workflows/release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index e2f9c02ffe..ca8d301d98 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -7,7 +7,7 @@ jobs: automate: runs-on: ubuntu-18.04 env: - RELEASE_TOKEN: ${{ secrets.RELEASE_TOKEN }} + RELEASE_TOKEN: ${{ secrets.GITHUB_TOKEN }} NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} FORCE_COLOR: 1 steps: