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

I just updated actions/deploy-pages to v4 and actions/upload-pages-artifact to v3 in my repo and got this error:

Run actions/deploy-pages@v4
Fetching artifact metadata for github-pages in run 7264600[9](https://github.com/AREA44/astro-research-theme/actions/runs/7264600911/job/19792767463#step:2:10)[11](https://github.com/AREA44/astro-research-theme/actions/runs/7264600911/job/19792767463#step:2:12)
Creating Pages deployment with payload:
{
	"artifact_id": 1[12](https://github.com/AREA44/astro-research-theme/actions/runs/7264600911/job/19792767463#step:2:13)45035[14](https://github.com/AREA44/astro-research-theme/actions/runs/7264600911/job/19792767463#step:2:15),
	"pages_build_version": "cf67bf05e7d24c255c38726ac891fe4b93fbf25b",
	"oidc_token": "***"
}
Error: Creating Pages deployment failed
Error: HttpError: No artifact_url provided
    at /home/runner/work/_actions/actions/deploy-pages/v4/node_modules/@octokit/request/dist-node/index.js:124:1
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at createPagesDeployment (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/api-client.js:68:1)
    at Deployment.create (/home/runner/work/_actions/actions/deploy-pages/v4/src/internal/deployment.js:78:1)
    at main (/home/runner/work/_actions/actions/deploy-pages/v4/src/index.js:30:1)
Error: Error: Failed to create deployment (status: 400) with build version cf67bf05e7d24c255c38726ac891fe4b93fbf25b. Responded with: No artifact_url provided

Full log here.

About this issue

Original URL
State: closed
Created 6 months ago
Reactions: 33
Comments: 17 (4 by maintainers)

Commits related to this issue

fix: restore deploy action v3 https://github.com/actions/deploy-pages/issues/284 https://github.com/actions/deploy-pages/issues/286 — committed to davwheat/rail-announcements by davwheat 6 months ago
Workaround for https://github.com/actions/deploy-pages/issues/284 — committed to bmccool/markdown-resume by bmccool 6 months ago

Most upvoted comments

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.

+10

JamesMGreene on Dec 20, 2023

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 on Dec 21, 2023

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

JamesMGreene on Dec 22, 2023

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.

JamesMGreene on Dec 20, 2023

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

davwheat on Dec 20, 2023

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.

luizrcs on Dec 20, 2023