From 6712a129d5ca9dfb4f840011d9ae184b78b8a488 Mon Sep 17 00:00:00 2001 From: jamiecobbett Date: Tue, 24 Mar 2026 10:29:36 +0000 Subject: [PATCH] Use the correct token for triggering publish The last time a version bump was merged, it created the git tag and github release, but it didn't trigger the maven-publish.yml flow to publish it to maven. I think this is because it used the standard GITHUB_TOKEN which can't trigger workflows. By using the GOCARDLESS_CI_ROBOT_TOKEN Personal Access Token, we can trigger workflows. --- .github/workflows/auto-release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/auto-release.yml b/.github/workflows/auto-release.yml index b1da17af..0128a964 100644 --- a/.github/workflows/auto-release.yml +++ b/.github/workflows/auto-release.yml @@ -42,4 +42,4 @@ jobs: git push origin v${{ steps.version.outputs.version }} gh release create v${{ steps.version.outputs.version }} --generate-notes env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + GITHUB_TOKEN: ${{ secrets.GOCARDLESS_CI_ROBOT_TOKEN }}