Remove duplicate package-manager declaration after relay merge - #42
Merged
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
1 participant
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.
The merge of relay qualification PR #39 with the independent pnpm-pin PR #41 left two identical
packageManagerkeys in the root manifest. Merged-main CI stopped at Biome's duplicate-key error before qualifying the real relay.Remove the duplicate declaration while retaining pnpm 10.33.2. No dependency, lockfile, protocol, production configuration or runtime change.
Validation: frozen managed install and full
pnpm checkpass, including 37 tests, server/web typechecks, build, coverage and existing code-health/security ratchets. Hosted CI must pass the actual network-isolated relay and iOS checks before merge; merged-main CI is checked again afterward.