34347168170
84%

Ran 09 Sep 2026 11:48AM UTC

Jobs 0

Files 0

Run time –

Badge

Embed ▾

pending completion

Build # 34347168170

Build Type

push

github

Committed by

web-flow

Commit Message

fix(release): sync server/test package versions to v3.0.0-prerelease.3 (#1507)

## What
Bring the published `mongodb-mcp-server` and the two test packages into
lockstep with the `v3.0.0-prerelease.3` release, and make
`prepare-release.yml` bump them automatically going forward.

- Bump `mongodb-mcp-server` to `v3.0.0-prerelease.3` and sync its
derived version fields (`packageInfo.ts`, mcpb `manifest.json`,
`server.json`).
- Rename `@mongodb-js/e2e-tests` → `@mongodb-js/mcp-e2e-tests` (package
name only; the `packages/e2e-tests` directory is unchanged) so it's
caught by the `@mongodb-js/mcp-*` glob.
- Bump `mcp-e2e-tests` and `@mongodb-js/harness-tester` to
`v3.0.0-prerelease.3`.

## Why
#1506 bumped the monorepo root + scoped `@mongodb-js/mcp-*` packages to
`v3.0.0-prerelease.3`, but the published `mongodb-mcp-server` package
was never bumped — it's unscoped, so the prepare-release `--filter
'@mongodb-js/mcp-*'` doesn't match it. Because the publish workflow
reads the version from `packages/mongodb-mcp-server/package.json`, run
34342866085 saw the still-existing `v3.0.0-prerelease.2` tag, set
`VERSION_EXISTS=true`, and skipped the release.

## How
`prepare-release.yml` now explicitly bumps `mongodb-mcp-server` and
`@mongodb-js/harness-tester` in addition to the `@mongodb-js/mcp-*`
glob. `e2e-tests` became `mcp-e2e-tests` so the glob covers it too.

Coverage Stats

Source Files on build 34347168170

Detailed source file information is not available for this build.

mongodb-js / mongodb-mcp-server / 34347168170
84%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on build 34347168170

mongodb-js / mongodb-mcp-server / 34347168170 84%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on build 34347168170

mongodb-js / mongodb-mcp-server / 34347168170
84%

README BADGES
x