Upload failed with warning: UPLOAD_MODE "release" was specified but no URL to upload to could be detected

[timabell]

Hi, thanks for creating this github action.

I've tried to set it up on this repo: https://github.com/timabell/gitopolis/actions (the main > release workflow yml files)

I've run into the following warning message and no release has appeared and I'm a bit stumped:

Warning: UPLOAD_MODE "release" was specified but no URL to upload to could be detected (build log)

I've followed the action's readme as best I can.

I see from

rust-build.action/entrypoint.sh

Line 61 in b369eae

UPLOAD_URL=$(echo "$EVENT_DATA" | jq -r .release.upload_url)

that it's trying to get release.upload_url from the event json file, and looking at my build output there's no mention of that. I'm not sure why it's not there.

It's a brand new and didn't have any releases. I created a "pre-release" release but that didn't help. (I wondered if github only set that up if you have any releases). I'll keep trying and post an update here for the benefit of the internet if I figure anything else out.

Research:

• https://www.freecodecamp.org/news/publishing-github-event-data-with-github-actions-and-pages/
  • https://docs.github.com/en/developers/webhooks-and-events/webhooks/about-webhooks#events=
    • https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#webhook-payload-example=

[Douile]

The workflow only has access to release data when triggered by a release event (you set which events trigger the workflow in the on section). You can only use the release mode when triggering with a release event otherwise please use a different upload mode.

[Gowee]

Hi.

In my case, releases are created by https://github.com/softprops/action-gh-release for pushed tags automatically. And the release event isn't triggered due to GitHub's limitations. Is it possible to allow setting UPLOAD_URL and RELEASE_NAME, so that users could specify them manually?

[thefireflyer]

Hi.

In my case, releases are created by https://github.com/softprops/action-gh-release for pushed tags automatically. And the release event isn't triggered due to GitHub's limitations. Is it possible to allow setting UPLOAD_URL and RELEASE_NAME, so that users could specify them manually?

Hi,
I'm not sure if this would work at all for your use case (or if this is still a relevant problem), but I managed to work around this issue by first compiling the files and storing them as artifacts, and then just using this library to publish those files.
Currently working implementation here
Hope this helps!

(@Gowee @AliSajid)

[AliSajid]

Hi.
In my case, releases are created by https://github.com/softprops/action-gh-release for pushed tags automatically. And the release event isn't triggered due to GitHub's limitations. Is it possible to allow setting UPLOAD_URL and RELEASE_NAME, so that users could specify them manually?

Hi, I'm not sure if this would work at all for your use case (or if this is still a relevant problem), but I managed to work around this issue by first compiling the files and storing them as artifacts, and then just using this library to publish those files. Currently working implementation here Hope this helps!

(@Gowee @AliSajid)

Thank you. Yes, I used this until I figured out that i plus also call this as a separate workflow when the release is published. That is also a neat workaround.