Skip to content

Node24 upgrade, update github actions to latest versions#229

Open
SrzStephen wants to merge 3 commits into
devcontainers:mainfrom
SrzStephen:node24-upgrade
Open

Node24 upgrade, update github actions to latest versions#229
SrzStephen wants to merge 3 commits into
devcontainers:mainfrom
SrzStephen:node24-upgrade

Conversation

@SrzStephen
Copy link
Copy Markdown

Closes #227

I see that #228 was created but never merged in.

@SrzStephen SrzStephen requested a review from a team as a code owner May 24, 2026 15:57
@SrzStephen
Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

"name": "Node.js & TypeScript",
// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
"image": "mcr.microsoft.com/devcontainers/typescript-node:1-20-bookworm",
"image": "mcr.microsoft.com/devcontainers/typescript-node:1-24-bookworm",
Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

If you wanted to while I'm at it I can change this to debian 13 (trixie) since it's the new LTS

Not an issue until June 30th, 2028 if you want to keep this small.

Comment thread yarn.lock

"@types/node@*", "@types/node@^18.11.18":
"@types/node@*":
version "18.11.18"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I am curious if this is the outcome if you just replace the version number in the package.json without actively uninstalling the former package 🤔 Have you tried to run "yarn remove ..." before? I am curious why yarn want's to keep the node@18 version in its yarn.lock - but I am honest, I work too less with yarn at the moment.

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.

Upgrade to Node24

2 participants