Fix release workflow failing due to branch protection issues #31
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.
Trying to fix the state of affairs: without providing any token for the
actions/checkout@v3
action step as well as if passing the built-insecrets.GITHUB_TOKEN
to it - the semantic release action later on would end up unauthorized to push changes tomaster
since it is set with branch protection, more reference for this issue on: semantic-release/semantic-release#2636 (comment).I've created a new
SEMANTIC_RELEASE_ACTION_PAT
secret for this repo as implied with some PAT I generated.Hope there will be a better way to work with Branch Protection some day...