Closed torn4dom4n closed 10 months ago
Also experiencing this: https://github.com/domstolene/designsystem/actions/runs/7264875307/job/19793326264
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 Please look into this issue as soon as possible. #287 seems to be a good fix.
It's currently 10pm in Minneapolis (where his GitHub profile says he's based). Be patient. Workarounds exist.
Oh, yeah. I forgot to check his timezone. I'm extremely sorry. Thank you for informing @davwheat :grin:!
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)
This is probably due to your workflows missing the newly required actions: read
permission for v4
.
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:
But, as a short-term workaround, I believe adding the actions: read
permission to your workflow/job will alleviate this blocker.
This is probably due to your workflows missing the newly required
actions: read
permission forv4
.
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
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
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.
Thanks for tracking this down! :)
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 Yes, it works now :+1: - https://github.com/SaptarshiSarkar12/Drifty/actions/runs/7283610116. Awesome support :clap:, thank you @JamesMGreene :grin:.
Confirming Github actions for the ledger/ledger.github.io repo are back to ✅. Thanks for resolving this, much appreciated 👍
📣 The latest release, v4.0.1
, has removed the need for the actions: read
permission that v4.0.0
introduced. 🪓
Error actions/checkout@v4, actions/configure-pages@v5, actions/upload-pages-artifact@v3, and actions/deploy-pages@v4 are not allowed to be used in hugolpz/SignesDeBibliotheques. Actions in this workflow must be: within a repository owned by hugolpz.
I went to and changed the option :
Settings > Actions > General
Actions permissions
(o) Allow all actions and reusable workflows
I just updated actions/deploy-pages to v4 and actions/upload-pages-artifact to v3 in my repo and got this error:
Full log here.