Node v26 not supported as described in `javascript-node` and `typescript-node`

[dslatkin]

In the README for javascript-node, typescript-node, it says:

Using this image

You can directly reference pre-built versions of Dockerfile by using the image property in .devcontainer/devcontainer.json or updating the FROM statement in your own Dockerfile to one of the following. An example Dockerfile is included in this repository.

• mcr.microsoft.com/devcontainers/typescript-node (latest)
• mcr.microsoft.com/devcontainers/typescript-node:26 (or 26-trixie, 26-bookworm to pin to an OS version)
• ...

But if you try to use mcr.microsoft.com/devcontainers/typescript-node:26 as the image in a dev container, you'll get an error that the image can't be found.

Linked to in that same README, referencing the full list of published image variants shows that tag 26 is not available as a standalone, it's only presently available under a dev- prefix:

    "dev-26",
    "dev-26-bookworm",
    "dev-26-trixie",

I'm not sure if there's some build process that creates these instructions or it's maintained manually but it would be nice if node v26, if mentioned, used the dev tag and were mentioned as not generally available or experimental or something.

Right now the easiest way to discover this is through failing to pull it as described which produces an error log like this:

[2026-08-18T13:00:30.392Z] Error: Command failed: docker pull mcr.microsoft.com/devcontainers/typescript-node:26
[2026-08-18T13:00:30.392Z]     at g9 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.466.0/dist/spec-node/devContainersSpecCLI.js:467:1277)
[2026-08-18T13:00:30.392Z]     at kv (/root/.vscode-remote-containers/dist/dev-containers-cli-0.466.0/dist/spec-node/devContainersSpecCLI.js:467:1021)
[2026-08-18T13:00:30.392Z]     at async M9 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.466.0/dist/spec-node/devContainersSpecCLI.js:486:4649)
[2026-08-18T13:00:30.393Z]     at async GI (/root/.vscode-remote-containers/dist/dev-containers-cli-0.466.0/dist/spec-node/devContainersSpecCLI.js:486:5768)
[2026-08-18T13:00:30.393Z]     at async I5 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.466.0/dist/spec-node/devContainersSpecCLI.js:667:206)
[2026-08-18T13:00:30.393Z]     at async a5 (/root/.vscode-remote-containers/dist/dev-containers-cli-0.466.0/dist/spec-node/devContainersSpecCLI.js:666:15743)
[2026-08-18T13:00:30.393Z]     at async /root/.vscode-remote-containers/dist/dev-containers-cli-0.466.0/dist/spec-node/devContainersSpecCLI.js:486:1917

[V-Subhankar-infy]

Hello Danny Slatkin (@dslatkin),

Thank you for reporting this.

This is a temporary discrepancy caused by our release cycle. The issue affects typescript-node only; Node 26 tags are already available for javascript-node, including [mcr.microsoft.com/devcontainers/javascript-node:26] (https://mcr.microsoft.com/en-us/artifact/mar/devcontainers/javascript-node/tag/26).

Node 26 support for typescript-node was added in PR #1946 on August 7, after the most recent monthly release. As a result, the stable mcr.microsoft.com/devcontainers/typescript-node:26 tag has not been published yet, although the preview dev-26 variants are currently available.

The stable typescript-node:26 image, along with the expected OS-specific tags, will be published in the next release, expected within the next few weeks.

[dslatkin]

Hi, thank you for commenting on this! I see, it makes sense why it’s not working given the release timing and how the ‎dev-26 variants are published ahead of the stable tag.

Is the README generated from the same source of truth as the MCR tags, or updated manually? If it’s automated, it might be worth delaying or annotating new versions in the README until the corresponding non‑‎dev tags are live.