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

feat(release)!: Remove contents: read permissions #95

Merged
merged 2 commits into from
Aug 27, 2024

Conversation

chris3ware
Copy link
Member

The release workflow uses a token generated from the 3ware release GitHub App, therefore should not need to use GITHUB_TOKEN permissions meaning all scopes can be disabled.

This workflow does not need to be able to read the contents of a
repository
This workflow uses a token generated from a GitHub App, so the default
`GITHUB_TOKEN` permissions do not apply.
@chris3ware chris3ware requested a review from a team as a code owner August 27, 2024 09:56
@james3ware james3ware merged commit 10aa9ec into main Aug 27, 2024
3 checks passed
@james3ware james3ware deleted the fix-token-permissions branch August 27, 2024 10:42
3ware-release bot pushed a commit that referenced this pull request Aug 27, 2024
## [3.0.0](v2.6.0...v3.0.0) (2024-08-27)

### ⚠ BREAKING CHANGES

* **release:** Remove `contents: read` permissions (#95)

### Features

* **release:** Remove `contents: read` permissions ([#95](#95)) ([10aa9ec](10aa9ec))
@3ware-release
Copy link
Contributor

3ware-release bot commented Aug 27, 2024

This PR is included in version 3.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants