mroberts 57e25f86f2 fix(ci): grant contents:write to the Gitea release job ...

The top-level `permissions: contents: read` added alongside the zizmor
hardening applies to the release job too, and Gitea honours it: the built-in
gitea-actions token became read-only, so `tea releases create` failed with
"user should have a permission to write to a repo" (run 759).

The .github workflow already narrowed write to its release job; the Gitea
workflow has a single job and was left read-only. Grant it contents: write,
keeping the read-only default at the top level.

2026-07-21 15:23:29 -05:00

..

ci.yml

ci: pin actions to SHAs and gate workflows on actionlint + zizmor

2026-07-21 15:16:55 -05:00

release.yml

fix(ci): grant contents:write to the Gitea release job

2026-07-21 15:23:29 -05:00