You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's not a question; I just wanted to share my experience, hoping it might help somebody. After several trial-and-error, I discovered that the new fine-grained personal access token didn't work for me, while the classic PAT worked just fine. In my case, I use my company's private repo, but the fine-grained PAT gives me access only to my repos, and that was the reason I couldn't access it, as far as I understand.
This is the error I got:
error=scm releases: failed to publish artifacts: could not release: POST https://api.github.com/repos/<company>/<project>/releases: 404 Not Found []
The bottom line is to use Classic PAT with GoReleaser on GitHub.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It's not a question; I just wanted to share my experience, hoping it might help somebody. After several trial-and-error, I discovered that the new fine-grained personal access token didn't work for me, while the classic PAT worked just fine. In my case, I use my company's private repo, but the fine-grained PAT gives me access only to my repos, and that was the reason I couldn't access it, as far as I understand.
This is the error I got:
error=scm releases: failed to publish artifacts: could not release: POST https://api.github.com/repos/<company>/<project>/releases: 404 Not Found []
The bottom line is to use Classic PAT with GoReleaser on GitHub.
Beta Was this translation helpful? Give feedback.
All reactions