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
https://github.com/IMB11/xanders-sodium-options/actions/runs/12333368646/job/34422360355
Error: HttpError: 400 (Bad Request, {"message":"You have sent an invalid request. Please do not send this request again.","request_id":"2FC0:33579C:84AFE8:912D63:675DFF3F","documentation_url":"https://developer.github.com/v3/"})
I adore the low-key threatening "Please do not send this request again."
Is this issue reproducible for you? I can't seem to trigger it on my end. Did it work previously? Could this be related to the token and/or its permissions?
Oh, I see now. If you take a closer look at the logs, you'll notice that the github-token input is not listed there. This occurs when the input receives an empty value (because GitHub treats an empty string as "unset", which forced me to use a special default value, ${undefined}, for each of my inputs). So, yeah, ${{ secrets.CLASSIC_GITHUB_TOKEN }} is empty in this context, meaning this is indeed a token issue. (Honestly, GitHub API error messages could use some work...)
If it weren't for a regression discussed in #106(already fixed in my local tree, so this will be resolved once I finalize v4), mc-publish wouldn't have even attempted to publish assets to GitHub.
Of course! I'm pretty sure everything will be up and running before 1.22 drops. It could have been much sooner, but I went through some tough times. Thankfully, things are a bit better now :)
Description
Expected Behavior
It uploading to github releases.
Actual Behavior
It doesnt.
Version
Latest - v3.3
Environment
GitHub Actions
Configuration
Logs
Other Information
No response
The text was updated successfully, but these errors were encountered: