microsoft / microsoft/vscode-remote-release
devcontainer-lock.json always get the end newline removed
Open
@chrmarti is already working on this.
Since Jul 25, 2026.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
GitHub reports files that don't end with an empty newline. All lockfile tools I've used (npm, pnpm, cargo) add this empty newline at the end by default. VSCode does not.
If I add the end newline manually, at the next run, VSCode will update the file and remove it again, even if no other change to the file (sha update, feature added/removed) was necessary.
- VSCode Version: 1.130.0
- Local OS Version: Windows 11
- Remote OS Version: GitHub Codespaces
- Remote Extension/Connection Type: Dev Containers
Steps to Reproduce:
- Open a repo in a devcontainer
- devcontainer-lock.json gets generated.
- Add an empty newline to the end of the file.
- Commit the file.
- Close the devcontainer and reopen it again. VSCode will remove your added newline, so the last line will always be the closing
}of the JSON file.
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.