Sometimes release creates as draft, but this is unexpected

[SNMetamorph]

[pzhlkj6612]

Hello.

I've encountered the same issue and have to sleep 60 seconds after removing old release (and tag) and before making new release (and tag). I think there might be something wrong on GitHub side.

[SNMetamorph]

Hello.

I've encountered the same issue and have to sleep 60 seconds after removing old release (and tag) and before making new release (and tag). I think there might be something wrong on GitHub side.

Thank you for such interesting information. Is yours hotfix works reliable?

[pzhlkj6612]

Is yours hotfix works reliable?

Well, I don't think it's reliable, but it has worked for me for the past 2 weeks.

Give it a try?

[yairm210]

Trying to understand the status of this bug: Is this still happening?

[rorgoroth]

Trying to understand the status of this bug: Is this still happening?

Yes, it just happened to me 1/2 days ago, also happened a few weeks ago. There was no release, but a draft with all the assets, here is the action run: https://github.com/rorgoroth/mingw-cmake-env/actions/runs/19521255843/job/55885031491

But nothing of value in the logs:

Run svenstaro/upload-release-action@latest
  with:
    repo_token: ***
    file: bin/*.7z
    tag: latest
    overwrite: true
    file_glob: true
Getting release by tag latest.
Release for tag latest doesn't exist - creating it
Uploading bin/xonotic.7z to xonotic.7z in release latest.
Uploading bin/quake3e.7z to quake3e.7z in release latest.
Uploading bin/quake3e-urbanterror.7z to quake3e-urbanterror.7z in release latest.
Uploading bin/quake3e-openarena.7z to quake3e-openarena.7z in release latest.
Uploading bin/quake2pro.7z to quake2pro.7z in release latest.
Uploading bin/mpv.7z to mpv.7z in release latest.
Uploading bin/ffmpeg.7z to ffmpeg.7z in release latest.
Uploading bin/ffmpeg-full.7z to ffmpeg-full.7z in release latest.

[yairm210]

🤔 In your case there is only a single Github API called to create the release, and it's sent without a draft parameter

So this is almost certainly a Github API issue. I assume behind the scenes they create a draft and then undraft it, and somehow the first part happens and the second errors.
The question is, can we detect and fix it? I think we can
After uploading the files, we can retrieve the new release, and if it's a draft and isn't supposed to be, we can send an update request to un-draft it

[yairm210]

The problem with such cases is that they're pretty much irreproducible, so it's hard for me to ensure as such that this solves the problem, so if you encounter any more cases where this happens please tell 🙏🏿

[rorgoroth]

Thanks, I'll keep an eye on it. This has only happened a handful of times this year, I thought it was my vpn being funny with github when using update scripts and only today just actually checked to find this issue happening. Now that I know, I will report back if it happens again.