fix: Use custom GitHub token to bypass branch protection #565
Conversation
This file contains 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
aorinevo
approved these changes
Dec 2, 2021
aorinevo
pushed a commit
that referenced
this pull request
Dec 3, 2021
# [1.16.0](v1.15.5...v1.16.0) (2021-12-03) ### Bug Fixes * Use custom GitHub token to bypass branch protection ([#565](#565)) ([2c17503](2c17503)) ### Features * Exclude archived repos when using code search ([#564](#564)) ([ec4fa27](ec4fa27)) * GitHub request throttling ([#551](#551)) ([b93d30e](b93d30e))
|
Looks like this worked - v1.16.0 was just published! |
|
🎉 This PR is included in version 1.16.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our few most recent commits to master have failed to publish because
semantic-releasecouldn't push new versions tomaster. Per https://github.com/semantic-release/semantic-release/blob/8fda7fd423d24e7b425fbee83790f49dd0478e2d/docs/recipes/ci-configurations/github-actions.md#pushing-packagejson-changes-to-a-master-branch, we should be settingpersist-credentials: falseduring checkout so that our custom token (that can bypass branch protection restrictions) is used bysemantic-release.