Skip to content

chore(deps): upgrade the MCP Apps extension SDK to 2.0.0 #2309

Closed
2 of 2 issues completed
Closed

Description

@github-actions

A new MCP Apps extension SDK release is out. What is installed on v2/main is behind what the npm registry publishes.

Package Declared Installed on v2/main Latest on npm Behind
@modelcontextprotocol/ext-apps ^1.7.4 1.7.5 2.0.0 yes

Release notes: https://github.com/modelcontextprotocol/ext-apps/releases

Why this is an issue and not a PR

Filed by the nightly SDK watch (#1063), the third of this repo's issue-filing sweeps alongside the monthly dependency refresh (#2229) and the daily Dependabot alert sweep (#2233). None of them opens a PR: a bot-authored PR carries no Closes #N and no board card, so the work would be invisible to the board. A maintainer picks this up and opens a normal PR against v2/main.

Upgrade checklist

  • Bump the version(s) in the repo-root package.json — every runtime dependency core/ imports is declared in the repo-root package.json and nowhere else (Dependency placement). The four typescript-sdk packages are pinned exactly, so they move together.
  • npm install at the root, and commit the refreshed lockfile.
  • Re-check the bundler external lists (clients/{cli,tui}/tsup.config.ts, clients/web/tsup.runner.config.ts) if the release adds or renames an entry point; npm run verify:bundle-externals enforces this against the built output.
  • npm run format, then npm run local:gate.

An automated review of what actually changed upstream — and which parts of this app it touches — is posted as a comment below.

A later run of this sweep will not refile this issue. A further SDK release files its own issue and leaves a supersession note here rather than editing this one.

Activity

  1. added this to the v2.6.0 milestone on Sep 10, 2026
  2. added
    dependenciesPull requests that update a dependency file
    v2Issues and PRs for v2
    choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior change
    on Sep 10, 2026
  3. cliffhall commented on Sep 11, 2026

    @cliffhall
    Member

    Triage: Priority Medium (total 8)

    • Severity 3 — a major SDK bump (ext-apps 1.7.5 → 2.0.0) that we are behind on; nothing is broken today, but the gap grows
    • Urgency 4 — tied to a dated external dependency (an upstream SDK release)
    • Bonuses: +1 already milestoned (v2.6.0) — i.e. already approved

    Board: #28, Status Todo (milestone was already set; only the card was missing — the nightly SDK watch has no org-project token).

  4. modified the milestones: v2.6.0, v2.7.0 on Sep 11, 2026
  5. cliffhall commented on Sep 11, 2026

    @cliffhall
    Member

    This was generated by our SDK watcher. Don't build from this, just take it as the signal to implement #1745

  6. self-assigned this
    on Sep 14, 2026
  7. cliffhall commented on Sep 14, 2026

    @cliffhall
    Member

    Shipped. @modelcontextprotocol/ext-apps is at 2.0.0 on v2/main via #2358 (#1745, the SDK-v1 shim removal) and #2361 (#2359, the stale sdk-watch wording). Both sub-issues are closed and every checklist item above is checked. The one cleanup the bump does not yet unlock — dropping the ext-apps#733 mirrors — is tracked separately as #2360, since no published release contains that PR.

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

Metadata

Metadata

Assignees

Labels

choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior changedependenciesPull requests that update a dependency filev2Issues and PRs for v2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions