Use latest v11 npm and set git safe.directory on build#2738
Merged
DocMoebiuz merged 3 commits intomainfrom Feb 22, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the frontend devcontainer bootstrap so new containers install the latest npm v11 (addressing lockfile peer=true behavior) and configure Git’s safe.directory to avoid “dubious ownership” errors during builds.
Changes:
- Add a global Git
safe.directoryentry duringpostCreateCommand. - Install latest npm v11 during devcontainer creation before running installs and Playwright setup.
|
Build for this pull request: |
|
Build for this pull request: |
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates the frontend devcontainer bootstrap so new containers install the latest npm v11 (addressing lockfile
peer=truebehavior) and configure Git’ssafe.directoryto avoid “dubious ownership” errors during builds.Changes:
safe.directoryentry duringpostCreateCommand.fixes #2730