-
Notifications
You must be signed in to change notification settings - Fork 117
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
I keep getting tags instead of releases #589
Comments
@Dun-sin have you found a solution to this issue? my semantic-release workflows started failing recently and I also don't understand the reason. The release commit and the tag are pushed to the repo, the new package version is published to npm, but creating a github release fails. |
@ianaa that's exactly what's happening to me, but sadly I haven't found a solution yet |
ensure that the token that you are providing to semantic-release has contents-write permission |
I cross-checked that, and the token has the proper permissions, do you think there's something else I'm missing? |
either your token does not have the proper permissions, or your pipeline is passing the wrong token to semantic-release. perhaps you need to set |
When Github says their fine grained access tokens are beta, they mean it. A heads up for anyone integrating Github plugins into your repository: do not use the fine grained access tokens. (They labeled by Github as beta) They create flustering results; for example, I have hunted through Github issues and tried various Github actions to determine why the skeleton repository's workflow's semantic-release job failed. Come to find out, the token didn't grant write access to the repository even though I authorized the token, the fine-grained token, for the repository. So I switched back to the classic token; the semantic-release job parsed the commits and published a release. 🙌:skin-tone-6: Oh, and Github fails with a 404 error. The only way I found the authorization error was I configured the workflow job to no longer persist credentials to the repository. Then the workflow provided a more descriptive error message: stderr: 'remote: Write access to repository not granted.\n'. After reading that I obliterated the fine-grain access token for a classic token. Everything worked perfectly. |
I think it's an issue from the project itself, because I didn't have to do anything, and it's working again |
Getting this error and I don't understand why
The text was updated successfully, but these errors were encountered: