devops -> main #51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "devops"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Manual PR after pipeline fix.
The 'Create Forgejo release + upload artifact' step has been failing with HTTP 403 'user should have a permission to write to a repo' because secrets.TAP_TOKEN is the maintainer's cross-repo token (write:repository scope on the homebrew tap) and does NOT have write permission on this akclip repo. Forgejo Actions injects ${{ github.token }} as the auto-token with write permission to the current repo. That's the right token for: - POST /repos/{owner}/{repo}/releases (release create) - POST /releases/{id}/assets (asset upload) - DELETE /repos/{owner}/{repo}/branches/... - POST /repos/{owner}/{repo}/issues/.../labels TAP_TOKEN is still used for the cross-repo tap sync, which is the only place a cross-repo write is required. This also brings the bottles job's FORGEJO_TOKEN in line with the release job's auto-token, so the entire in-repo release path uses one identity.Pull request closed