-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to V4 broke the deploy step #286
Comments
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 |
Just another same here https://github.com/wildfly/wildfly-maven-plugin/actions/runs/7270026747. Could this potentially be related to actions/download-artifact#249? |
You correctly identified the first issue that workflows will need the newly required 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 The second issue you're hitting is a bit more of a mystery offhand. We'll investigate today! 🔍 |
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 |
We believe this should be resolved as of ~4 hours ago, assuming you also include the |
Still failing on v4 here https://github.com/ollegkz/olle.coffee/actions/runs/7285230140 (with read permissions for actions) :( |
@ollegkz You need to update your build job to use |
Aww, long wait then I guess D: https://github.com/withastro/action/blob/main/action.yml#L96. Thanks for the explanation <3 |
📣 The latest release, |
Initial failure with permissions:
resulted in:
After updated the permissions to:
New failure:
The text was updated successfully, but these errors were encountered: