Greptile Summary

This PR bumps @microsoft/teams.apps from 2.0.5 to 2.0.6 in the extensions/msteams package. The key upstream change in v2.0.6 is the removal of the problematic '/api*' wildcard Express route that was incompatible with Express 5 / path-to-regexp v8, replacing it with an explicit registerRoute call. As a side-effect, teams.apps no longer declares @microsoft/teams.api, @microsoft/teams.common, and @microsoft/teams.graph as peer dependencies — they are now bundled directly — which removes the entire Express 4.x transitive dependency tree from the lockfile (-212 lines).

• The lockfile update is clean and consistent with the version bump.
• All Express 4.x packages ([email protected], [email protected], [email protected], etc.) are correctly removed.
• Minor cleanup opportunity: @microsoft/teams.api in package.json remains at 2.0.5 while @microsoft/[email protected] now brings in @microsoft/[email protected] as its own bundled dep, leading to both versions being installed. Bumping the direct dep to 2.0.6 would keep all @microsoft/teams.* packages in sync.

Confidence Score: 5/5

• This PR is safe to merge — it is a well-scoped dependency bump with a passing test suite and a net reduction in transitive dependencies.
• The change is a single-package version bump that resolves a known Express 5 incompatibility. All 338 msteams tests pass, the lockfile reduction is consistent with the claimed change, and no logic has been modified. The only finding is a non-blocking P2 suggestion to align @microsoft/teams.api to 2.0.6 to avoid a dual-version installation.
• No files require special attention.

This is a comment left during a code review.
Path: extensions/msteams/package.json
Line: 7

Comment:
**`@microsoft/teams.api` version not bumped to match**

`@microsoft/teams.api` is still pinned at `2.0.5` here while `@microsoft/[email protected]` now bundles `@microsoft/[email protected]` as a direct (non-peer) dependency. This causes pnpm to install both versions simultaneously — `2.0.5` for direct usage in this package, and `2.0.6` inside `teams.apps`.

For a patch-level bump the types are very likely compatible, and the passing tests confirm no runtime breakage. But bumping to `2.0.6` here too would eliminate the duplicate installation and keep all `@microsoft/teams.*` packages aligned:

```suggestion
    "@microsoft/teams.api": "2.0.6",
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "chore(msteams): bump @microsoft/teams.ap..." | Re-trigger Greptile}

Good catch — bumped @microsoft/teams.api to 2.0.6 as well in 07505cb to eliminate the dual-version installation. All 338 msteams tests still pass.

Closing — these changes were superseded by main. The @microsoft/teams.apps and @microsoft/teams.api 2.0.6 bumps were included in 10527ff ("build: refresh deps and vitest cache lanes") merged to main on Mar 27. The PR diff is now empty.