[codex] Isolate Qwen source checkout in desktop release#12
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.
Summary
Root cause
The workflow previously checked out qwen-code-source below the OpenWork workspace. After OpenWork ran bun install, TypeScript in qwen-code-source could walk up to the parent node_modules/@types tree and pick up OpenWork's @types/node, which can pollute Qwen Code source type checks.
Validation
Note: this isolates the source checkout from OpenWork dependencies. If the selected Qwen Code ref has package.json and package-lock.json out of sync, npm ci will still fail correctly.