ci(update-audit): post issues with gitea_token (has write:issue) #68

Merged

k.renner merged 1 commits from update-audit-use-gitea-token into master

2026-06-27 07:48:19 +00:00

Author	SHA1	Message	Date
k.rennerandClaude Opus 4.8	dd32b5d917	ci(update-audit): post issues with gitea_token (has write:issue) ci/woodpecker/manual/update-audit Pipeline was successful Details security_bot_token is scoped for code/PRs only; the issue POST in the post step returned HTTP 403 'token does not have ... write:issue', so the audit ran green but silently created no issue. Switch GITEA_TOKEN to the gitea_token secret — the broader machine account already used by build-caddy and build-ci-images for release-asset and registry writes — which is the most likely existing secret to also hold write:issue. No new token to provision; audit issues become attributed to gitea_token's owner instead of the security bot. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-27 09:36:12 +02:00

Author

SHA1

Message

Date

k.rennerandClaude Opus 4.8

dd32b5d917

ci(update-audit): post issues with gitea_token (has write:issue)

ci/woodpecker/manual/update-audit Pipeline was successful

Details

security_bot_token is scoped for code/PRs only; the issue POST in the
post step returned HTTP 403 'token does not have ... write:issue', so the
audit ran green but silently created no issue. Switch GITEA_TOKEN to the
gitea_token secret — the broader machine account already used by
build-caddy and build-ci-images for release-asset and registry writes —
which is the most likely existing secret to also hold write:issue.

No new token to provision; audit issues become attributed to gitea_token's
owner instead of the security bot.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-27 09:36:12 +02:00