Fix specification builds #281
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since the last release the GitHub Actions environment has changed such that we now must explicitly grant permissions to actions in order to make a release. Signed-off-by: Joshua Lock <[email protected]>
joshuagl
force-pushed
the
joshuagl/gh-actions-perms
branch
from
1380d3d to
a531332
Compare
Member
Author
|
Hi @lukpueh, @mnm678, @trishankatdatadog -- I'd appreciate a quick review on this one. Our last set of changes are not reflected in the published spec because the GHA doesn't work without this permission being granted. |
joshuagl
commented
May 15, 2023
lukpueh
previously approved these changes
May 15, 2023
Explain why we need `contents: write` Signed-off-by: Joshua Lock <[email protected]>
lukpueh
approved these changes
May 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Something changed in our GitHub Actions environment (either the platform itself or our organisation's default permissions) since the last specification release such that the build and publish workflow has failed for the most recent change.
This PR is the simplest fix, adding the required permissions for the workflow to succeed.