Support: javascript-node 24 #1423
Conversation
|
@microsoft-github-policy-service agree |
Marukome0743
force-pushed
the
pr1423
branch
2 times, most recently
from
2dc9b34 to
714baa8
Compare
|
Just curious, is this blocked by anything in particular, such as v24 becoming LTS? Or is it simply waiting for availability to review? |
## Summary Add Node.js 24 support to JavaScript and TypeScript devcontainer images and update defaults and documentation accordingly. New Features: - Add support for Node.js 24 variants (24-bookworm and 24-bullseye) in both javascript-node and typescript-node images Enhancements: - Set the default 'latest' variant and devcontainer ARG to 24-bookworm Build: - Update manifest.json files to include new 24 variants with architectures and variantTags Documentation: - Update README files to list and reference the new 24 image tags and adjust security patching examples
There was a problem hiding this comment.
As a reply to #1423 (comment)
(Disclaimer: it is late and I am relatively new to the org)
It seems like there is a need for the JS version to be published before we can move onto the typescript variant. What I will ask you to do is: remove all Typescript changes, we will publish the JS ones and then make another PR for TS which we can deal with once the former has been merged and released (I will do by EOD Monday).
Marukome0743
changed the title
|
Thank you for a nice review! On the other hand, I will make the another typescript 24 PR. |
|
|
Summary
Introduce Node.js 24 on both Debian Bookworm and Bullseye, make it the default variant, and update documentation and tag configurations accordingly.
New Features:
24-bookwormand24-bullseye) in the JavaScript Node imageEnhancements:
24-bookwormto the default (latest) variantVARIANTin the devcontainer Dockerfile to24-bookworm