-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
announce: Node.js 22 release announcement #6661
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
7756c58
to
f735459
Compare
@marco-ippolito I've edited the PR description to include the link to the release or for better reference and easier navigation |
f735459
to
3c0abb5
Compare
Co-authored-by: Tobias Nießen <[email protected]> Signed-off-by: Marco Ippolito <[email protected]>
Co-authored-by: Joyee Cheung <[email protected]> Signed-off-by: Marco Ippolito <[email protected]>
e1f310a
to
16dfddc
Compare
16dfddc
to
6302191
Compare
Co-authored-by: Geoffrey Booth <[email protected]> Signed-off-by: Marco Ippolito <[email protected]>
Co-authored-by: Geoffrey Booth <[email protected]> Signed-off-by: Marco Ippolito <[email protected]>
Lighthouse Results
|
Signed-off-by: Marco Ippolito <[email protected]>
Signed-off-by: Marco Ippolito <[email protected]>
Signed-off-by: Marco Ippolito <[email protected]>
@nodejs/nodejs-website is there something to trigger manually or its just taking some time? |
I think because d77ead9 was pushed we need to retrigger the actions with the
github_actions:pull-request
|
I've no idea what the remaining "Lint" status is waiting for. 😞 |
Release announcement for Node 22
@RafaelGSS
Release PR: