Images have moved to https://github.com/devcontainers/images #532
Description
UPDATE - Images previously built out of this repository are now at https://github.com/devcontainers/images
New tracking issue is devcontainers/images#90
Original text:
The following are release dates and EOL / end of support dates for languages / OS's with pre-built images. After runtime or OS support for a given image has ended, we will stop building images for that version. We also typically only release images for "LTS" or "stable" releases of runtimes/OS's. Others can be built from .devcontaiiner/base.Dockerfile available in the definition source code in this repository.
Releases typically happen monthly on the same release cadence as VS Code and include the most recent changes from the upstream base image or runtime version including security updates (e.g. the latest OS updates and the latest point release of a runtime or platform). You can see the current schedule for the VS Code release in a pinned "Iteration Plan" issue at the VS Code repository. We may update earlier if a critical need or bug is discovered.
Dev container images are also versioned independent of the runtime. To avoid unexpected breaks, we recommend pinning to the latest major version of an image release to pick up security and feature updates without breaking changes. This image version number is a prefix to the variant or runtime version. e.g. mcr.microsoft.com/vscode/devcontainers/typescript-node:0-14 where 0 is the major version number of the dev container image. This happens automatically when using the Add Development Container Configuration Files... command in the Remote - Containers extension or GitHub Codespaces.
To make pinning to a version easier if you wish to do so, recent versions of images include a devcontainer-info command that will output information about the image in use including version information and a link to a file with additional information on contents.
Note that in some cases, we may have to end support earlier than the stated date below if there are fundamental OS requirements that force it or if the primary extension(s) supporting it have dropped support. In these cases, there would no longer be a functioning VS Code story. Our expectation is that this should be rare given typical GA to EOL timelines and is something we strive to avoid.
Rust (mcr.microsoft.com/vscode/devcontainers/rust), Anaconda (mcr.microsoft.com/vscode/devcontainers/anaconda), and Miniconda (mcr.microsoft.com/vscode/devcontainers/miniconda), and Jekyll (mcr.microsoft.com/vscode/devcontainers/jekyll) have an ongoing release schedule, so we are continually releasing the latest stable version. The Jekyll image also includes the github-pages gem for Jekyll 3.x.