-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⚠️ Currently broken due to defunkt Basic Auth APIs #351
Comments
For anyone else seeing this - I messed around with this for a good 30 minutes. You'll need to run |
Any update? Could we use a workaround of asking for the user to supply the github token instead of the username and password to bridge the gap similar to how the app asks for the Circle CI token? |
Yeah that would be good for the time being. PR welcome |
worked around via #352 |
semantic-release-cli
is currently not working, as it utilizes basic auth for authentication, which is no longer supported by GitHub.Until we resolve this issue by implementing a OAuth web flow, this is what my usual release GitHub action looks like:
https://github.com/octokit/core.js/blob/master/.github/workflows/release.yml
You don't need to configure the GITHUB_TOKEN, it's already provided. Unless you have actions triggered by the release event, in which case you need to use a personal access token, because actions don't trigger actions.
Hope that helps. Let me know if you have any questions
The text was updated successfully, but these errors were encountered: