Skip to content

chore: refresh dependencies and apply available security fixes - #994

Draft
Aamir Jawaid (heyitsaamir) wants to merge 1 commit into
mainfrom
heyitsaamir-dependency-security-updates
Draft

Aamir Jawaid (heyitsaamir) wants to merge 1 commit into
mainfrom
heyitsaamir-dependency-security-updates

Conversation

@heyitsaamir

Copy link
Copy Markdown
Collaborator

Summary

Refresh compatible workspace dependencies and remediate the available npm audit fixes without downgrading Jest or the bot SDKs. Audit is not clean: 42 findings become 11 high findings (9 with --omit=dev), all rooted in the same unpatched Zod 3 advisory. This PR remains a draft because that blocker is unresolved.

Public API change — dependency baseline: @microsoft/teams.apps and @microsoft/teams.common now require Axios ^1.21.1 for their HTTP functionality instead of ^1.20.0, ensuring installations cannot select the older baseline. This is a compatible minor dependency update; exported signatures and caller configuration are unchanged, and no caller migration is required. Other published exports and peer dependency ranges are unchanged.

Implementation details

1. Refresh compatible dependencies

Raise the Hono server/framework and TypeScript ESLint minimums to patched releases, and refresh the lockfile within existing workspace ranges. This also updates Azure identity/MSAL, MCP, OpenAI, Vite, and related tooling. The lockfile was freshly resolved with npm 11.12.1 because incremental installation retained vulnerable versions despite root overrides; its larger diff includes hoisting and deduplication changes.

2. Patch blocked transitive dependencies

Use scoped overrides for Agents hosting's MSAL Node 7.2.3 and Microsoft's HTTP instrumentation 0.222.0. Move vulnerable glob consumers to 14.0.6 and test-exclude's minimatch to 11.0.9, retaining the existing UUID security override. These repository-root overrides repair this development graph; they do not propagate into consumers' independent dependency trees.

3. Preserve compatibility boundaries

Keep OpenTelemetry API below 1.10.0 because the installed 2.x SDKs require that range; a newer API copy can silently disable telemetry. HTTP client/server spans were also checked using a real local request. Defer TypeScript 7, ESLint 10, SignalR 11, tsup 9, and other out-of-range migrations rather than mixing them into security maintenance.

Remaining blocker

BotBuilder, Microsoft Agents SDK, and the React compiler ESLint plugin still depend on vulnerable Zod 3. Their supported releases have no patched Zod 3 replacement, and their existing schema/error APIs are incompatible with a forced Zod 4 substitution. Upstream migrations or separately reviewed integration changes are needed before npm audit can pass; findings are neither suppressed nor reclassified.

Update compatible workspace dependencies and resolve patched MSAL, HTTP instrumentation, glob, and minimatch transitive dependencies. Preserve the OpenTelemetry API version supported by the installed SDKs. Upstream Zod 3 dependencies still prevent a clean npm audit.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant