[ferrlabs-renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@ferrlabs/mcp-core (source)	^10.14.0 → ^10.14.3

---

Release Notes

FerrLabs/MCP (@​ferrlabs/mcp-core)

v10.14.3

Compare Source

Bug Fixes

• fix(transport): validate the bearer before building a server (#​474)

v10.14.2

Compare Source

Bug Fixes

• fix(core): reject dot segments in API request paths (#​470)

v10.14.1

Compare Source

Bug Fixes

• fix(deps): override vulnerable transitive deps flagged by pnpm audit (#​469)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Every minute (* * * * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[ferrfleet-interne]

Patch bump of @ferrlabs/mcp-core (10.14.0 → 10.14.2). Manifest and lockfile agree: specifier, resolution, and snapshot all moved together, and the transitive @modelcontextprotocol/sdk stays at 1.32.1. The new ajv-formats peerDependencies block is only lockfile metadata (optional ajv peer) and resolves nothing new. Nothing blocking. CI was still running when I reviewed.

[ferrfleet-interne]

Re-checked after the rebase to 10.14.3. The manifest specifier and the lockfile importer, resolution and snapshot all moved together. The transitive @modelcontextprotocol/sdk stays at 1.32.1, and the earlier ajv-formats lockfile churn is gone. Nothing blocking.

Nit: the PR title still says ^10.14.2 while the diff pins ^10.14.3. Renovate normally fixes this on its next pass, but check it before squash-merging so the commit message is accurate.

CI was still running when I reviewed.