From e1192a2014da8acfea37c5319f0b612f9f5a392e Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Sun, 18 Oct 2026 18:28:41 +0200 Subject: [PATCH] fix(ci): point release-please at PR_GITEA_TOKEN (write scopes) The dedicated RELEASE_PLEASE_TOKEN_CV_SITE_NUXT secret authenticated for reads but threw when creating the release PR (exit 1, releases_created false, no PR created): it lacks write:repository / write:issue. Use the proven PR_GITEA_TOKEN instead, per the one-well-scoped-token policy in OKF_Nuxt/decisions/snyk-paused-and-secrets-policy.md. --- .gitea/workflows/release-please.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/release-please.yml b/.gitea/workflows/release-please.yml index 9f874d2..185d3e0 100644 --- a/.gitea/workflows/release-please.yml +++ b/.gitea/workflows/release-please.yml @@ -15,6 +15,13 @@ jobs: steps: - uses: joaquinjsb/gitea-release-please-action@v4 with: - token: ${{ secrets.RELEASE_PLEASE_TOKEN_CV_SITE_NUXT }} + # One well-scoped token for all workflow API work (see + # OKF_Nuxt/decisions/snyk-paused-and-secrets-policy.md). The + # dedicated RELEASE_PLEASE_TOKEN_CV_SITE_NUXT secret failed with + # exit 1: reads worked (createReleases completed) but creating + # the release PR threw - the token lacked the write:repository / + # write:issue scopes. PR_GITEA_TOKEN has both and is proven by + # the AI-review comment posting. + token: ${{ secrets.PR_GITEA_TOKEN }} config-file: release-please-config.json manifest-file: .release-please-manifest.json -- 2.54.0