chore(release): prepare v0.4.0

[jonathanMLDev]

Added: Multi-source mode (PINECONE_SOURCES, list_sources, etc.)
Changed (breaking types): Branded CoreServerConfig / AllianceServerConfig
Changed (internal): Response schema consolidation (no MCP payload change)

Summary by CodeRabbit

• Documentation

  • Updated release notes, README, and migration guidance for version 0.4.0.
  • Added clearer upgrade instructions, including multi-source mode and breaking type changes.
  • Refreshed install, CLI, and deployment examples to use 0.4.0.

• Chores

  • Bumped the package version to 0.4.0 and updated compare links for the new release.

[coderabbitai]

Warning

Review limit reached

@jonathanMLDev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 765616b9-a55e-49e8-875f-4f7f14cd0083

📥 Commits

Reviewing files that changed from the base of the PR and between e04aec6 and 92b24bc.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (3)

• src/cli.ts
• src/core/server/source-tool-utils.ts
• src/core/server/tools/keyword-search-tool.ts

📝 Walkthrough

Walkthrough

This PR bumps the package version from 0.3.0 to 0.4.0 across package.json, README.md, CHANGELOG.md, docs/MIGRATION.md, and docs/deprecation-policy.md, updating installation examples, migration section labels, changelog entries, and compare links accordingly.

Changes

0.4.0 Release Version Bump

Layer / File(s)	Summary
Package version bump package.json	Version field updated from 0.3.0 to 0.4.0.
Changelog entry and compare links CHANGELOG.md	0.4.0 entry reworked with split "Breaking (types)" and "Library (internal)" bullets, updated migration links, and revised Unreleased/0.4.0 compare URLs.
Migration guide section labels docs/MIGRATION.md	Multi-source Pinecone and Branded ServerConfig types section headings relabeled from "Unreleased" to "0.4.0".
README version references and install examples README.md	Current version, new "Upgrading to 0.4.0" section, and npm/yarn/pnpm/global/Claude Desktop/CLI/deploy examples updated to pin @0.4.0.
Deprecation policy example version docs/deprecation-policy.md	Example pinned version updated from 0.3.0 to 0.4.0.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• cppalliance/pinecone-read-only-mcp-typescript#184: Prior release-documentation update touching the same version-pinning/upgrade surface in README, CHANGELOG, and docs/deprecation-policy.md.

Suggested reviewers: AuraMindNest, wpak-ai

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely reflects the release preparation for v0.4.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@f09d35c). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #190   +/-   ##
=======================================
  Coverage        ?   83.86%           
=======================================
  Files           ?       45           
  Lines           ?     2306           
  Branches        ?      768           
=======================================
  Hits            ?     1934           
  Misses          ?      372           
  Partials        ?        0           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.