Skip to content

Remove uses of kPromiseResolveAfterResolved and kPromiseRejectAfterResolved#253

Merged
o- merged 1 commit into
v8:node-ci-2026-04-16from
bakkot:promise-resolve-after-resolve-enum
May 11, 2026
Merged

Remove uses of kPromiseResolveAfterResolved and kPromiseRejectAfterResolved#253
o- merged 1 commit into
v8:node-ci-2026-04-16from
bakkot:promise-resolve-after-resolve-enum

Conversation

@bakkot
Copy link
Copy Markdown

@bakkot bakkot commented May 6, 2026

@google-cla
Copy link
Copy Markdown

google-cla Bot commented May 6, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@bakkot bakkot force-pushed the promise-resolve-after-resolve-enum branch from 38ea2df to e66f17a Compare May 6, 2026 03:09
Copy link
Copy Markdown
Member

@o- o- left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks

@o-
Copy link
Copy Markdown
Member

o- commented May 11, 2026

Actually, this should go into the node-ci-2026-04-16 branch.

@bakkot bakkot changed the base branch from main to node-ci-2026-04-16 May 11, 2026 13:35
this was Co-Authored-By: Felipe Coelho <felipecoelho.ness@gmail.com>
@bakkot bakkot force-pushed the promise-resolve-after-resolve-enum branch from e66f17a to 867e3a0 Compare May 11, 2026 13:42
@o- o- merged commit 89bcbbf into v8:node-ci-2026-04-16 May 11, 2026
1 check passed
@bakkot bakkot deleted the promise-resolve-after-resolve-enum branch May 11, 2026 16:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants