GitHub Actions GITHUB_TOKEN lost permissions because unspecified scopes were set to none
If you specify the access for any of these permissions, all of those that are not specified are set to `none`.
GitHub Actions can unexpectedly lose needed GITHUB_TOKEN scopes when a workflow declares specific permissions, because all unspecified permissions are then set to none.
If you specify the access for any of these permissions, all of those that are not specified are set to `none`authentication
Observed message
If you specify the access for any of these permissions, all of those that are not specified are set to `none`.
Why it happens
The workflow sets one or more permissions explicitly and assumes the rest keep their defaults.
A job or workflow uses the permissions key without listing all required scopes.
An action requires contents, pull-requests, or another scope that was implicitly removed.
How to fix it
List every required permission explicitly whenever you use the permissions key.
Check which API or action capability failed and map it to the missing token scope.
Use least privilege, but make the required permission set complete rather than partial by accident.
