Skip to content
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

Closed
gr2m opened this issue Nov 20, 2020 · 5 comments
Closed

⚠️ Currently broken due to defunkt Basic Auth APIs #351

gr2m opened this issue Nov 20, 2020 · 5 comments

Comments

@gr2m
Copy link
Member

gr2m commented Nov 20, 2020

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

@gr2m gr2m pinned this issue Nov 20, 2020
@gr2m gr2m changed the title ⚠️ Currently brokend due to defunkt Basic Auth APIs ⚠️ Currently broken due to defunkt Basic Auth APIs Nov 20, 2020
@exbotanical
Copy link

exbotanical commented Nov 22, 2020

For anyone else seeing this - I messed around with this for a good 30 minutes. You'll need to run semantic-release, not semantic-release-cli setup. Do semantic-release --gh-token=yourtoken (add npm token if needed - mine was already set in npmrc).

@cujarrett
Copy link
Contributor

cujarrett commented Jan 2, 2021

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?

@gr2m
Copy link
Member Author

gr2m commented Jan 2, 2021

Yeah that would be good for the time being. PR welcome

@cujarrett
Copy link
Contributor

@gr2m - Please let me know if it looks off.

#352

@gr2m
Copy link
Member Author

gr2m commented Jan 3, 2021

worked around via #352

@gr2m gr2m closed this as completed Jan 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants