Repository navigation
Conversation
Refresh compatible transitive security fixes and override the SDK's vulnerable Zod pin without changing the Vally versions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
Address the shared
npm audit --audit-level=moderatefailure in Agent Harness Coverage observed on #39400 and #39409. The vulnerable dependency graph is already present on main; neither PR introduced it.@github/copilot-sdk@1.0.15, which otherwise pins vulnerable Zod 4.3.6. The patched Zod is deduplicated across the graph; remove the override when the upstream SDK pin is patched.Feed ingestion blocker
This PR is a draft because ingestion is not complete.
The requested target is dnceng/public/dotnet-public-npm. fast-uri 3.1.9, qs 6.16.1, and Zod 4.6.7 were downloaded through that feed using fresh caches, and their archive integrity matches both this lockfile and npmjs.
body-parser 2.4.0 exists on npmjs but returns 404/not-found through the selected feed. Authenticated npm resolution,
npm cache add, installation, and the documented Azure Artifacts content-download API could not retrieve it. The feed reports a healthy npmjs upstream and the caller has the Collaborator role; 2.4.0 is not present even when including deleted versions. The underlying feed-side cause is not yet established. No feed policy was changed and no package was manually republished.Keep the PR in draft until body-parser 2.4.0 has also been saved from npmjs into the selected feed and its archive integrity verified.
Validation
npm ciusing the public npmjs registry succeeds under Node 24.22.1.npm audit --audit-level=moderate --registry=https://registry.npmjs.org: zero vulnerabilities.npm test: 69 passed, none failed or skipped.npm run lint: passed for all 18 components.Separately, Dependabot already updates
/eng/harness-evaluationweekly on Monday; adding a duplicate npm configuration is unnecessary. Automated security-update settings, upstream exact pins, and feed-ingestion automation can be investigated independently of this dependency fix.