Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Scope in GITHUB_ACTIONS Checks #419

Closed
1 task done
satellite-no opened this issue May 2, 2024 · 3 comments
Closed
1 task done

Missing Scope in GITHUB_ACTIONS Checks #419

satellite-no opened this issue May 2, 2024 · 3 comments

Comments

@satellite-no
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Reports an error unknown permission scope "attestations" which is incorrect.

Expected Behavior

Should validate like all other scopes.

Super-Linter version

v6.4.1

Relevant log output

### Failed Workflow:

  .github/workflows/upload-deploy.yml:18:7: unknown permission scope "attestations". all available permission scopes are "actions", "checks", "contents", "deployments", "discussions", "id-token", "issues", "packages", "pages", "pull-requests", "repository-projects", "security-events", "statuses" [permissions]
     |
  18 |       attestations: read
     |       ^~~~~~~~~~~~~
  ------


### Following Workflow without attestations:
```text
Invalid workflow file: .github/workflows/upload-deploy.yml#L14
The workflow is not valid. .github/workflows/upload-deploy.yml (Line: 14, Col: 3): Error calling workflow 'org/repo/.github/workflows/lint-package-inspect.yml@b7547c86547eee07595a5f8cb0a9eed2737c7a2b'. The workflow is requesting 'attestations: read', but is only allowed 'attestations: none'.


### Steps To Reproduce

add below to `jobs` section.
```yaml
  lint-package-inspect:
    uses: ./.github/workflows/lint-package-inspect.yml
    permissions:
      actions: read
      attestations: read

Anything else?

NA

@satellite-no
Copy link
Author

Reference from upstream super-linter/super-linter#5601

@hugovk
Copy link

hugovk commented May 2, 2024

@rhysd
Copy link
Owner

rhysd commented May 2, 2024

This is already fixed by #418 and it will be included in the next release.

@rhysd rhysd closed this as completed May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants