fix: preserve market peer policy in generation installs - #394
Merged
Conversation
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.
Desktop discarded the market’s
--config.auto-install-peers=falseretry option when converting an install into an isolated generation. Installing@kenz1117/dsh-ui-usage-billing@1.2.5could therefore keep fetching an obsolete host peer and fail on the unpublisheddsh-type-metadependency even after the market requested recovery.Forward the explicit boolean peer policy to the generation pnpm subprocess, supporting both kebab-case and camelCase. When omitted, inherit the Profile workspace’s explicit autoInstallPeers boolean so release-age recovery cannot consume the only retry before peer recovery. Without either setting pnpm retains its default. This is a targeted contract fix, not arbitrary pnpm argument forwarding or a change to third-party market code. Only the peer boolean is inherited; workspace paths and upstream version re-resolution are outside this change.
Validation: