chore: Allow CI to push updates to package.json
#123
Merged
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.
🎉 releases are now being published to NPM.
However the bump commit to update package.json with the new version number cannot be pushed to
main
because the branch is protected.Following this doc https://github.com/semantic-release/semantic-release/blob/master/docs/recipes/ci-configurations/github-actions.md#pushing-packagejson-changes-to-a-master-branch I need someone with the power to add a repo secret
GITHUB_TOKEN
containing a Personal Access Token with the corresponding permissions to push tomain
bypassing the protected branch rules.TODO
RELEASE_GITHUB_TOKEN
to repo secrets