You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After looking at #521 and seeing that @actions/core has already been updated on master, I saw that the package action has been broken for some time. This means that changes to any of the javascript code never make it to dist.
Expected Behavior
Code that reaches master should be packaged automatically
Current Behavior
The package action fails with this error:
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: 3 of 3 required status checks are expected. At least 1 approving review is required by reviewers with write access.
To https://github.com/aws-actions/configure-aws-credentials
! [remote rejected] HEAD -> master (protected branch hook declined)
error: failed to push some refs to 'https://github.com/aws-actions/configure-aws-credentials'
Error: Process completed with exit code 1.
Thanks for reporting this @sindrig, this occurred when we updated the branch protection rules recently (code has to be merged in a PR and cannot be pushed directly). We're working on figuring out the best permanent solution, but in the meantime we can probably do this manually.
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
After looking at #521 and seeing that @actions/core has already been updated on master, I saw that the package action has been broken for some time. This means that changes to any of the javascript code never make it to dist.
Expected Behavior
Code that reaches master should be packaged automatically
Current Behavior
The package action fails with this error:
Example run
Reproduction Steps
Not applicable - is broken on master
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: