fix: move github token to env for semantic release #241
Conversation
This file contains hidden or 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
Lash-L
force-pushed
the
Lash-L-patch-9
branch
from
3c7855b to
c05b31c
Compare
humbertogontijo
approved these changes
Nov 14, 2024
|
Sorry this is being way more involved than I thought it would be Could you try following these instructions semantic-release/github#175 (comment) If you make the GH_TOKEN, I could do the rest, or you could modify it directly yourself if you'd like, up to you. But I don't have permissions to do that. |
|
I think GH_TOKEN was already set. But I regenerated the token and set a new value to it |
|
There's also a PYPI_TOKEN env variable available |
|
Theoretically, pypi token shouldn't be needed. Right now it is just having failures pushing the new version commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.