Failing to fetch artifact metadata since 4.0.0

[TheMrMilchmann]

Failing to fetch artifact metadata since 4.0.0

[JamesMGreene]

Yup, we've identified an issue on the API internal side. A fix is in progress and should be rolled out in the next few hours. Thank you all for your reporting and patience, and our apologies for the temporary inconvenience! 🙇

P.S. If anyone needs a short-term workaround, please revert to using the previous major versions of actions/upload-pages-artifact and actions/deploy-pages until we can get the fix shipped.

[JamesMGreene]

We believe this should be resolved as of ~4 hours ago, assuming you also include the actions: read permission (for now). Please give it another try, but do let us know if you still encounter friction. 🙇

[luizrcs]

Same here, and it was driving me crazy until I saw these issues, as I thought I was simply missing something obvious on the setup. I checked the failed job logs and it says explicitly right at the beginning the pages write permission is given.

[JamesMGreene]

@TheMrMilchmann Good question. I was planning on proceeding with #288 in either case, but I've gone ahead and added a more specific bug for tracking that:

• #289

Thanks!

[JamesMGreene]

This is probably due to your workflows missing the newly required actions: read permission for v4.

https://github.com/actions/deploy-pages/pull/283/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R33

We're going to investigate removing the need for that new permission in an in-flight follow-up PR today, so please bear with us:

• #288

But, as a short-term workaround, I believe adding the actions: read permission to your workflow/job will alleviate this blocker.

[luizrcs]

This is probably due to your workflows missing the newly required actions: read permission for v4.

https://github.com/actions/deploy-pages/pull/283/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R33

We're going to investigate removing the need for that new permission in an in-flight follow-up PR today, so please bear with us:

• Use the Actions artifacts client to avoid needing the actions: read permission #288

But, as a short-term workaround, I believe adding the actions: read permission to your workflow/job will alleviate this blocker.

That solved the first issue for me, which was the 403 error, but now I'm getting a 400 "No artifact_url provided" like another issue mentioned.

[TheMrMilchmann]

Thanks for the update! I can confirm that this is working now after adding the actions: read permission. Should this issue be kept open for now because it's technically not resolved yet (but hopefully with #288)?

[JamesMGreene]

📣 The latest release, v4.0.1, has removed the need for the actions: read permission that v4.0.0 introduced. 🪓