f06ae3c4bc
CI / benchmark-publish (pull_request) Has been skipped
CI / push-validation (pull_request) Successful in 26s
CI / helm (pull_request) Successful in 32s
CI / build (pull_request) Successful in 52s
CI / lint (pull_request) Failing after 1m4s
CI / quality (pull_request) Successful in 1m29s
CI / typecheck (pull_request) Successful in 1m35s
CI / security (pull_request) Successful in 1m43s
CI / coverage (pull_request) Has been skipped
CI / integration_tests (pull_request) Successful in 3m38s
CI / e2e_tests (pull_request) Successful in 4m19s
CI / unit_tests (pull_request) Successful in 5m4s
CI / docker (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 3s
GitCheckoutHandler.discover_children() and FsDirectoryHandler.discover_children() now call discover_devcontainers() after scanning for fs-directory children. Any .devcontainer/devcontainer.json or root-level .devcontainer.json found at the resource location is registered as a devcontainer-instance child resource with provisioning_state: discovered. Named configurations are also discovered and carry the configuration name in the config_name property. This wires the previously-isolated discover_devcontainers() function into the production code path, enabling the spec's zero-configuration devcontainer experience. ISSUES CLOSED: #4740