chore(conformance): bump the vulnerable harness dependencies #615
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!615
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-581-harness-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
npm audit fixinconformance/mcp-client/, all within the ranges inpackage.json, which is unchanged. The lockfile moves @hono/node-server 1.19.14 to 1.19.17, fast-uri 3.1.3 to 3.1.8, hono 4.12.29 to 4.13.9, ip-address 10.2.0 to 10.7.2, and qs 6.15.3 to 6.16.0.npm audit: 0 vulnerabilities.osv-scanner scan source -r .: 0 vulnerabilities acrossgo.mod(36 packages) andpackage-lock.json(92 packages).npm cisucceeds, and the gate is green, including the MCP conformance run.Closes #581
Closes #581