-
Notifications
You must be signed in to change notification settings - Fork 519
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
🌱 Fix goreleaser permissions #984
Conversation
Integration tests success for 1d31de436c7912707bc9eeb26058249962e2afc3 |
* Fix the goreleaser permissions to read contents and write deployments
1d31de4
to
2477d11
Compare
Integration tests success for 2477d1172ccdac85095db3e1d4a6723198289e4d |
Not yet ready, figuring out the right permissions. |
@@ -19,6 +19,18 @@ on: | |||
tags: | |||
- "*" # triggers only if push new tag version, like `0.8.4` or else | |||
|
|||
permissions: | |||
actions: none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same comment as other PR. You can remove the name: none
ETA on this PR? |
this is interesting https://github.com/apps/step-security |
The hard thing with this is to only make releases to determine the right permissions. |
Integration tests success for 95db6ac782b31bc94606a187120ff4b987170f53 |
It will be addressed by #1164 |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
What is the current behavior? (You can also link to an open issue here)
Scorecard repo fails at
Token-Permissions
with score0
#942What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
No