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.
Description
This PR reverts to PR #1411. Sorry, I had a misunderstanding about the current workflow's structures... πββοΈ
The workflow
upload-artifacts.yaml
is called from the parent workflowrelease.yaml
. And the parent workflowrelease.yaml
has the configuration ofpermissions
.So, the
upload-artifacts.yaml
can run with the samepermissions
settings that are inherited fromrelease.yaml
. Therefore, we don't need to setpermissions
on theupload-artifacts.yaml
side explicitly.FYI: The action ran properly when we released
v3.10.2
yesterday, without the fixes of #1411. Also from this log, we can see that we don't need the fix of #1411.https://github.com/scalar-labs/scalardb/actions/runs/7322292094
Related issues and/or PRs
#1411
Changes made
upload-artifacts.yaml
file.Checklist
Additional notes (optional)
N/A
Release notes
N/A