fix(ci): drop the workflow permissions field - Forgejo ignores it with a warning #306

Merged
hexajon merged 1 commit from refs/pull/306/head into main 2026-07-20 19:37:55 +00:00
hexajon commented 2026-07-20 19:37:46 +00:00 (Migrated from codeberg.org)

Summary

Yesterday's CI hardening (4888f3b1) added GitHub-style least-privilege permissions: contents: read blocks to ci.yml and drift.yml. Forgejo does not support the permissions field: 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.

## Summary Yesterday's CI hardening (4888f3b1) added GitHub-style least-privilege `permissions: contents: read` blocks to ci.yml and drift.yml. Forgejo does not support the `permissions` field: 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.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sixfold-space/madtea!306
No description provided.