Add devcontainer-lock.json file#171982
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a .devcontainer/devcontainer-lock.json file to pin the resolved Dev Container feature digest, keeping Dev Container rebuilds consistent as newer VS Code/Dev Containers tooling begins generating this lock file.
Changes:
- Add
.devcontainer/devcontainer-lock.jsonlockingghcr.io/devcontainers/features/github-cli:1to a specific published SHA256 digest. - Record integrity metadata for the locked feature to ensure reproducible builds.
balloob
approved these changes
May 23, 2026
Crocmagnon
approved these changes
May 23, 2026
edenhaus
approved these changes
May 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
I had to rebuild my devcontainer today. It seems that with one of the recent updates to VSCode, they have now started to generate this file on builds, as this will impact all new and rebuilds. It should be committed to the codebase with the current values it generates.
I have verified that the sha it generated matches what has been published to ghcr for the feature referenced.
An alternative to this approach is to add this file to .gitignore.
The change was done here devcontainers/cli#1212
Type of change
Additional information
.devcontainer/devcontainer-lock.jsonto the repository #170914Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: