-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
deps: patch V8 to 12.4.254.16 #52845
Conversation
Review requested:
|
@aduh95 Now I know why we didn't specify a commit message in the action settings. |
Maybe related: there's the following error in the output of the action:
https://github.com/nodejs/node/actions/runs/8958849424/job/24603576667 |
That error was expected (I had reset the GH Actions cache). |
Here's a run on my fork with debug logs enabled: https://github.com/targos/node/actions/runs/9050008411/job/24864881790 Relevant:
So, I think there are two bugs:
|
With proper git setup: https://github.com/targos/node/actions/runs/9050110263/job/24865219130 For some reason, the action doesn't consider the new commit as a local change:
|
Maybe we should just use |
I'll try https://github.com/peter-evans/create-pull-request on my fork. It seems more maintained. |
This is an automated patch update of V8 to 12.4.254.16.