From a27bbbb2abf0fa8ddedd20c05bba2128e88faa3a Mon Sep 17 00:00:00 2001 From: Noel Sabia Date: Sun, 18 Oct 2026 19:41:33 +0200 Subject: [PATCH] fix(ci): give release-please git credentials for the release-branch push The 401 in run 89 was the final isomorphic-git push inside code-suggester's createPullRequest, not an API call: tree, commit and local ref update all ran through the token-authenticated octokit API, then 'git push' used the git-username/git-password inputs - unset in our workflow, so the push was anonymous. The remote branch release-please--branches--main still sat at an old commit, proving the push never landed. Pass the account name and the same token. --- .gitea/workflows/release-please.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.gitea/workflows/release-please.yml b/.gitea/workflows/release-please.yml index 185d3e0..511b856 100644 --- a/.gitea/workflows/release-please.yml +++ b/.gitea/workflows/release-please.yml @@ -23,5 +23,14 @@ jobs: # 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