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
Originally posted by MattiDragon January 20, 2024
I'm using this action, wrapped in a custom workflow that does other things. I recently updated my version from v3.2 to v3.3.0 and something seems to have broken with the handling of missing tokens. One my projects isn't published on curseforge, so I don't provide a token or project it in its workflow. This used to work, but now I'm getting an error that the curseforge project doesn't exist. This shouldn't happen as no token is provided, unless mc-publish decided to pick up the unused CURSEFORGE_TOKEN actions secret without me giving it as input (the token is there because I sync my tokens to all mods that need any of them). I'm just confused as to where mc-publish is getting something it thinks is a curseforge token (it should ignore empty strings, right?)
The text was updated successfully, but these errors were encountered:
Discussed in #103
Originally posted by MattiDragon January 20, 2024
I'm using this action, wrapped in a custom workflow that does other things. I recently updated my version from
v3.2
tov3.3.0
and something seems to have broken with the handling of missing tokens. One my projects isn't published on curseforge, so I don't provide a token or project it in its workflow. This used to work, but now I'm getting an error that the curseforge project doesn't exist. This shouldn't happen as no token is provided, unless mc-publish decided to pick up the unusedCURSEFORGE_TOKEN
actions secret without me giving it as input (the token is there because I sync my tokens to all mods that need any of them). I'm just confused as to where mc-publish is getting something it thinks is a curseforge token (it should ignore empty strings, right?)The text was updated successfully, but these errors were encountered: