Repository navigation
Fix WebMCP Key discovery and approval errors; patch redirect dependency - #238
Merged
Merged
Conversation
chen21019
changed the title
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.
Restricted API Keys gain explicit name-based discovery in the shared WebMCP browser/stdio contract, preserving ordinary-Key default discovery and native owner/type boundaries. Human confirmation failures now use clear fixed permission or stale-session guidance in all thirteen locales, retaining the existing alert and saving lifecycle. Follow-redirects is updated to the official 1.16.2 patch for CVE-2026-116689.
The npm12 verifier accepts only lock-proven aliases and exactly validated calculated advisory structures; it preserves raw reports, distinct advisory causes and all existing High/Critical, review-expiry and package-closure gates. Portable primary reports prove the vulnerable lock still fails and the patched lock has no High/Critical finding; 63 Moderate entries remain visible.
Validation: resource/audit 39 cases, confirmation/error/locale 6 cases, audit-policy 29 existing plus 10 new cases all pass in their directly affected source checks. Official cross-realm redirect regressions show RED before and GREEN after the patch. The new confirmation cases and portable audit cases are wired into the required full producer. Web Console 1.6.203/bridge0.2.5 publication, exact-artifact QA8080 audit/role/layout workflows and assembled Server acceptance remain pending. No production changes, policy widening, raw-ID shortcut or full-frontend completion claim.