Skip to content

Release v2.5.0 #5572

Closed
Closed

Description

@cliffhall

Tracks the v2.5.0 milestone release: the audit, the version PRs (Version Packages, Prepare Python Release), the v2/main → main merge PR, the release ledger, and the Release. Closed by hand once the Release is published.

Activity

  1. added this to the v2.5.0 milestone on Nov 18, 2026
  2. self-assigned this
    on Nov 18, 2026
  3. added
    choreMaintenance: deps, build tooling, CI, cleanup — no user-facing behavior change
    on Nov 18, 2026
  4. cliffhall commented on Nov 18, 2026

    @cliffhall
    MemberAuthor

    Release audit (step 2a)

    Audited at origin/v2/main 4b6f0954.

    Ecosystem Scope Result
    npm root lockfile (all four TypeScript workspaces), npm audit --audit-level=high 25 high, all one advisory: picomatch GHSA-fc5q-39xc-vjpf (ReDoS through single-branch repeated extglobs) and the packages that depend on it
    npm the same lockfile, npm audit --omit=dev found 0 vulnerabilities
    PyPI mcp-server-fetch locked requirements, pip-audit --require-hashes No known vulnerabilities found
    PyPI mcp-server-git locked requirements No known vulnerabilities found
    PyPI mcp-server-time locked requirements No known vulnerabilities found

    Every Python server was audited (verdict present for each).

    The picomatch finding: no fix available, and not reachable from a server

    • No patched release exists. The advisory's range is <= 4.0.7 with no first patched version, and 4.0.7 is the registry's latest. The lockfile resolves picomatch@4.0.7 (six copies) and 2.3.2 (one, under micromatch). The only "fix" npm offers is npm audit fix --force, which downgrades vitest to 3.1.4; that is ruled out (AGENTS.md Dependencies).
    • It is in development tooling only. npm ls picomatch --omit=dev is empty: it arrives through vitest/vite/tinyglobby, typescript-eslint, @changesets/cli and shx. No published package depends on it, so nothing this release publishes carries it. The globs those tools match are the repository's own.

    Outcome: nothing to change. No fixes were forced, so there is no audit PR. No tracking issue for the advisory exists yet; the daily alert sweep is the one that files a no-patched-release advisory for a decision.

  5. linked a pull request that will close this issuechore: version packages #5537on Nov 18, 2026
  6. linked a pull request that will close this issuechore: version packages #5597on Nov 18, 2026
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 changev2

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions