-
Notifications
You must be signed in to change notification settings - Fork 0
fix(scan): surface yarn PnP refusal instead of silent success-0 across all modes #201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Mikola Lysenko (mikolalysenko)
merged 3 commits into
main
from
fix/yarn-pnp-scan-silent-noop
Aug 19, 2026
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
7e442ba
test(e2e): RED — pin yarn PnP scan silent no-op + unreachable apply r…
mikolalysenko cd894fe
fix(scan): surface yarn PnP refusal instead of silent success-0 acros…
mikolalysenko a67d718
Merge remote-tracking branch 'origin/main' into fix/yarn-pnp-scan-sil…
mikolalysenko File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next
Next commit
test(e2e): RED — pin yarn PnP scan silent no-op + unreachable apply r…
…efusal On any yarn Plug'n'Play project, all three scan modes exit 0 / status=success / scannedPackages=0 with no warning (the crawler leg is empty because node_modules is absent, and the lockfile-supplement leg swallows the flavor probe's PnP diagnosis), and apply exits 0 with the calm noManifest status because the documented yarn_pnp_unsupported refusal sits below the noManifest early-return — unreachable when scan never wrote a manifest. These tests fail on current main (7 failed / 20 passed / 3 ignored): - scan --json --yes --mode agent|hosted|vendored on a PnP fixture must surface an explicit warnings[] refusal (exit semantics deliberately unchanged) and touch no file - human-mode scan must print the refusal to stderr - the pnpm node-linker=pnp twin surfaces its own diagnosis - apply --json / human with NO manifest must refuse loudly with the existing yarn_pnp_unsupported envelope, not silent noManifest Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- Loading branch information
commit 7e442ba53707be6d1baffbc443ebdac2295dd43d
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.