NOTE: Most of the contents of this repository have been migrated to the new devcontainers GitHub org (https://github.com/devcontainers). See https://github.com/devcontainers/template-starter and https://github.com/devcontainers/feature-starter for information on creating your own!
The problem: Most (if not all) container definitions include extensions from the VS marketplace to enable core scenarios like per-test run/debug, syntax highlighting, etc. If one of these extensions becomes abandoned, or archived (as was the case in #1253 ), maintainers of the images won't get automatically notified.
Proposal: Include, as part of scheduled automated CI runs, a report that iterates through all the manifests in this repository and looks for extensions that are out of date or should be otherwise retired.
The problem: Most (if not all) container definitions include extensions from the VS marketplace to enable core scenarios like per-test run/debug, syntax highlighting, etc. If one of these extensions becomes abandoned, or archived (as was the case in #1253 ), maintainers of the images won't get automatically notified.
Proposal: Include, as part of scheduled automated CI runs, a report that iterates through all the manifests in this repository and looks for extensions that are out of date or should be otherwise retired.
Some signals we could look for (input requested):
Relates to: Both