on: push: branches: - main permissions: contents: write pull-requests: write name: release-please jobs: release-please: runs-on: ubuntu-latest steps: - uses: joaquinjsb/gitea-release-please-action@v4 with: # 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 }} # The PR-creation path (code-suggester) pushes the release branch # with isomorphic-git using these git credentials - NOT the token # input (octokit reads use the token; the final `git push` uses # git-username/git-password). Unset, the push is anonymous and # fails "HTTP Error: 401 Unauthorized" after the branch commit is # already built. Gitea git-over-HTTPS auth: account name + # token as password. git-username: Noel git-password: ${{ secrets.PR_GITEA_TOKEN }} config-file: release-please-config.json manifest-file: .release-please-manifest.json