fix(ci): drop the workflow permissions field - Forgejo ignores it with a warning #306
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!306
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/306/head"
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?
Summary
Yesterday's CI hardening (
4888f3b1) added GitHub-style least-privilegepermissions: contents: readblocks to ci.yml and drift.yml. Forgejo does not support thepermissionsfield: every run now warns "not supported in Forgejo and will be ignored. Use Authorized Integrations to grant capabilities to this job instead." The field was a no-op plus warning noise on Codeberg.Removed the block from both workflows and left a comment in its place so the field is not re-added on a platform that ignores it; token capabilities are scoped on the forge via Authorized Integrations instead.