search

w3c / spec-prod

GitHub Action to build ReSpec/Bikeshed specs, validate output and publish to GitHub pages or W3C
https://w3c.github.io/spec-prod/
MIT License
34 stars 21 forks source link

Bad request - pnpm/action-setup@v3 is not allowed to be used in w3c/webdriver #178

Closed whimboo closed 7 months ago

whimboo commented 7 months ago

GitHub actions as triggered via the workflow currently fail for the WebDriver repository: https://github.com/w3c/webdriver/actions/runs/8688977311/job/23863799091

Download action repository 'actions/checkout@v2' (SHA:ee0669bd1cc54295c223e0bb666b733df41de1c5)
Download action repository 'w3c/spec-prod@v2' (SHA:071d7ebeafd4e6389a1fb2476f6eb93c958135ba)
Getting action download info
Error: Bad request - pnpm/action-setup@v3 is not allowed to be used in w3c/webdriver. Actions in this workflow must be: within a repository owned by w3c, created by GitHub, or matching the following: pnpm/action-setup@v2.

We did not make any changes, but I can see that on April 10th a dependency upgrade was merged, which bumps pnpm/action-setup@v2 to version 3.

@sidvishnoi can you please take a look or advice what to do to get the workflow running again? Thanks!

sidvishnoi commented 7 months ago

@whimboo You'll need to update allowed actions in webdriver repo settings. I'd recommend allowing w3c/spec-prod (all versions) and not configuring individually actions to avoid such issue in future.

To clarify, this isn't an issue with spec-prod, but rather customized permissions in WebDriver repo.

jgraham commented 7 months ago

Note that this is the wrong diagnosis; WebDriver was configured to allow all w3c actions, but only pnpm/action-setup@v2. Updating that to pnpm/action-setup@v3 should hopefully fix the problem.