Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
3 tasks done
andreynering opened this issue Aug 4, 2022 · 1 comment
Open
3 tasks done

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

andreynering opened this issue Aug 4, 2022 · 1 comment
Assignees
@per1234
Labels
topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project

Comments

@andreynering
Copy link
Contributor

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
@andreynering andreynering added the type: imperfection Perceived defect in any part of project label Aug 4, 2022
@per1234 per1234 self-assigned this Aug 4, 2022
@per1234 per1234 added the topic: code Related to content of the project itself label Aug 4, 2022
@felladrin
Copy link

I've just been through this issue.
image
Re-running the failed GitHub Job resolved the issue, as that version was published one minute after I got this error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@per1234 per1234

Labels
topic: code Related to content of the project itself type: imperfection Perceived defect in any part of project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@felladrin @andreynering @per1234