Compare commits

..
2 Commits
Author SHA1 Message Date
Noel 0e5ddda59d Merge pull request 'fix(ci): give release-please git credentials for the release-branch push' (#9) from fix/release-please-git-credentials into main
release-please / release-please (push) Successful in 6s
Reviewed-on: #9
2026-10-18 18:53:54 +00:00
Noel Sabia a27bbbb2ab fix(ci): give release-please git credentials for the release-branch push
PR Check / Dependency audit (pull_request) Failing after 9s
PR Check / Dockerfile lint (droast) (pull_request) Failing after 4s
PR Check / Security scan (Snyk) (pull_request) Skipped
PR Check / ESLint (pull_request) Successful in 35s
PR Check / Typecheck (pull_request) Successful in 38s
PR Check / Secret scan (gitleaks) (pull_request) Successful in 6s
PR Check / AI code review (opencode) (pull_request) Successful in 28s
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.
2026-10-18 19:41:33 +02:00
+9
View File
@@ -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