Actions fail after update actions/deploy-pages to v4 and actions/upload-pages-artifact to v3

[torn4dom4n]

Actions fail after update actions/deploy-pages to v4 and actions/upload-pages-artifact to v3

[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. 🙇

[JamesMGreene]

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

[davwheat]

It's currently 10pm in Minneapolis (where his GitHub profile says he's based). Be patient. Workarounds exist.

[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]

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.

[petter]

Also experiencing this: https://github.com/domstolene/designsystem/actions/runs/7264875307/job/19793326264

[SaptarshiSarkar12]

Same here - https://github.com/SaptarshiSarkar12/Drifty/actions/runs/7270487603

[SaptarshiSarkar12]

@JamesMGreene Please look into this issue as soon as possible. #287 seems to be a good fix.

[SaptarshiSarkar12]

Oh, yeah. I forgot to check his timezone. I'm extremely sorry.
Thank you for informing @davwheat 😁!

[orhun]

Same error here: https://github.com/orhun/git-cliff/actions/runs/7274801940/job/19821456493

[afh]

Ledger's project website https://ledger-cli.org is also affected by this (see https://github.com/ledger/ledger.github.io/actions/runs/7272871676/job/19828971150)

[davwheat]

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

I noticed the docs PR and tried this, but it also didn't help for me. See: https://github.com/davwheat/rail-announcements/actions/runs/7270687779

Workflow: https://github.com/davwheat/rail-announcements/blob/4e2b36306630d1fdfe825e658677979e392a65b7/.github/workflows/smoketest.yml#L89-L92

[mikesprague]

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

This also did not work for me. Same error as without it:

Fetching artifact metadata for pages-api-endpoints in run 7278395179
Creating Pages deployment with payload:
{
	"artifact_id": 1[12](https://github.com/mikesprague/api/actions/runs/7278395179/job/19832554835#step:5:13)705[13](https://github.com/mikesprague/api/actions/runs/7278395179/job/19832554835#step:5:14)38,
	"pages_build_version": "8aff0377aa9ad37ed46fce84654616e21a0f4cd0",
	"oidc_token": "***"
}
Error: Creating Pages deployment failed
Error: HttpError: No artifact_url provided

[davwheat]

Thanks for tracking this down! :)

[SaptarshiSarkar12]

@JamesMGreene Yes, it works now 👍 - https://github.com/SaptarshiSarkar12/Drifty/actions/runs/7283610116.
Awesome support 👏, thank you @JamesMGreene 😁.

[afh]

Confirming Github actions for the ledger/ledger.github.io repo are back to ✅. Thanks for resolving this, much appreciated 👍