Bug: 404 when tag was pushed but release not published yet

[andreynering]

Describe the problem

I just noticed an temporary issue that, when I push a new tag this action start breaking with a 404 error.

That happens because it can take some time until the CI finishes running and creates a draft release. I then have to manually publish that release so the artifacts become available.

To reproduce

Expected behavior

I know it may be an uncommon problem, but if easy it would be nice if this action used the releases endpoint from the GitHub API instead of the tags one. This means it'd fetch the previous release until the new one is not yet published.

'arduino/setup-task' version

v1.0.1

Additional context

No response

Issue checklist

• I searched for previous reports in the issue tracker
• I verified the problem still occurs when using the latest version
• My report contains all necessary details

[felladrin]

I've just been through this issue.

Re-running the failed GitHub Job resolved the issue, as that version was published one minute after I got this error.

[cvirtucio]

my team is was running into this issue, as well. re-running the job doesn't fix it, unfortuntaely:

[trim21]

#1193 will fetch versions from github releases instead of git tags, should fix thix

[trim21]

any chance get a review on #1193?