Fix shadowenv trust error in new git worktrees#6820
Open
Conversation
Why: When developers created new git worktrees, they encountered: "shadowenv failure: directory '.shadowenv.d' contains untrusted shadowenv program" This happened because .shadowenv.d/yarn.lisp was committed to the repo, but shadowenv trust files are user-specific and not tracked by git. New worktrees got the lisp file but no trust, causing the error. How: Remove the committed shadowenv files and add .shadowenv.d/ to .gitignore. The yarn deprecation wrapper and pnpm alias scripts are no longer needed since the pnpm migration completed in 2022. Going forward, `dev up` will generate shadowenv files as needed and handle trust automatically. Files removed: - .shadowenv.d/yarn.lisp (shadowenv config) - .shadowenv.d/.gitignore (kept yarn.lisp tracked) - bin/shadowenv/yarn (yarn deprecation warning) - bin/shadowenv/p (pnpm alias)
Contributor
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success3718 tests passing in 1438 suites. Report generated by 🧪jest coverage report action from b800136 |
graygilmore
approved these changes
Feb 5, 2026
EvilGenius13
approved these changes
Feb 5, 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
WHY are these changes introduced?
When developers create new git worktrees in this repo, they see:
This doesn't happen in other Shopify repos. The root cause:
.shadowenv.d/yarn.lispwas committed to git (added in 2022 for acceptance tests), but shadowenv trust files are user-specific and not committed. New worktrees get the lisp file but no trust → error.WHAT is this pull request doing?
Removes the committed shadowenv files and adds
.shadowenv.d/to.gitignoreas a safeguard..shadowenv.d/yarn.lisp.shadowenv.d/.gitignorebin/shadowenv/yarnbin/shadowenv/ppnpmdirectly).gitignore.shadowenv.d/to prevent reintroductionGoing forward,
dev upwill generate shadowenv files as needed and handle trust automatically.How to test your changes?
git worktree add ../test-worktree maincd ../test-worktreedev up- should work normallygit worktree remove ../test-worktreeMeasuring impact
Checklist