ci: release-please bumps 0.x minor and advertised version

[duyetbot]

Summary

• Yes: release-please owns tags and version bumps. Standing PR is #242 (chore(main): release X.Y.Z). A human merge tags vX.Y.Z and publishes the GitHub Release. Not auto-merged.
• bump-patch-for-minor-pre-major is now false, so in 0.x feat → minor (0.1 → 0.2) and fix → patch. After this lands, the next release-please run will rewrite chore(main): release 0.2.0 #242 to 0.2.0 (there have been feats since 0.1.4).
• Advertised version is no longer hardcoded 0.1.0. /api and MCP serverInfo read packages/api/src/lib/version.ts (currently 0.1.4). extra-files also update version.txt, the stdio MCP package, and dashboard package.json version on the release PR.

Test plan

• cd packages/api && bunx vitest run test/health.test.ts test/mcp.test.ts (15 passed)
• After merge, confirm release-please updates chore(main): release 0.2.0 #242 to chore(main): release 0.2.0 (do not merge that PR here)
• After a human merges the release PR, confirm tag v0.2.0 and /api reports "version": "0.2.0" on the following deploy

Summary by Sourcery

Centralize product versioning and wire the API, MCP server, and docs to the release-please managed semver rather than hardcoded values.

New Features:

• Expose the current product semver via the /api health endpoint and MCP server info using a shared VERSION constant.

Enhancements:

• Inject the runtime VERSION into the OpenAPI spec info.version field to keep the spec in sync with releases.
• Align MCP server and package versions to the current product semver and mark them for automated release-please updates.
• Document how release-please manages versions, tags, and the standing chore(main): release X.Y.Z PR, including 0.x bump behavior.

Build:

• Add version.txt and a VERSION source file so release-please extra-files can consistently update advertised versions across packages.

CI:

• Update release-please workflow and core-memory notes to use the built-in GITHUB_TOKEN and clarify manual merge requirements for release PRs.

Documentation:

• Update API reference and knowledge docs to describe the version field semantics and release-please driven versioning model.

Tests:

• Adjust API and MCP tests to assert against the shared VERSION constant instead of hardcoded version strings.

[sourcery-ai]

Sorry @duyetbot, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 46 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 27d27154-5221-4de2-863c-6414a0c2f623

📥 Commits

Reviewing files that changed from the base of the PR and between 5c905ba and b4a2b4d.

📒 Files selected for processing (13)

• .github/release-please-config.json
• .github/workflows/release-please.yml
• docs/api-reference.md
• docs/knowledge/core-memory.md
• packages/api/src/content/openapi.ts
• packages/api/src/index.ts
• packages/api/src/lib/version.ts
• packages/api/src/routes/mcp/index.ts
• packages/api/test/health.test.ts
• packages/api/test/mcp.test.ts
• packages/mcp/package.json
• packages/mcp/src/index.ts
• version.txt

---

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.}

[sourcery-ai]

Reviewer's Guide

Wire the public API and MCP server to a single source-of-truth product version constant managed by release-please, update Release Please configuration and documentation to reflect the 0.x semver bump rules and workflow, and adjust tests and docs accordingly.

File-Level Changes

Change	Details	Files
Expose product version from a single VERSION constant and use it in the HTTP /api response, OpenAPI spec, and MCP server info.	Introduce VERSION constant in a new version library module for the API. Use VERSION instead of a hardcoded string in the /api health endpoint response. Wrap OpenAPI JSON parsing so that info.version is dynamically set from VERSION. Use VERSION for MCP serverInfo instead of a hardcoded version string.	packages/api/src/lib/version.ts packages/api/src/index.ts packages/api/src/content/openapi.ts packages/api/src/routes/mcp/index.ts
Align tests and documentation with the new version source-of-truth and current product version.	Update API and MCP tests to assert the VERSION constant rather than a literal version value. Refresh API reference and OpenAPI examples to show the current version and explain the release-please-driven semver behavior. Update core maintenance knowledge docs to describe the new Release Please setup and version flow.	packages/api/test/health.test.ts packages/api/test/mcp.test.ts docs/api-reference.md docs/knowledge/core-memory.md
Update Release Please workflow, configuration, and package versions to support 0.x minor bumping and extra-files rewriting.	Modify the release-please GitHub Action comments to describe the standing release PR workflow, human-only merges, and 0.x bump rules. Configure release-please to use the GitHub-provided token and extra-files so it rewrites version.txt and code comments marked for version replacement. Bump the MCP package version and server info to the current product version with release-please markers. Add a top-level version.txt file as an extra-file target and ensure MCP package.json and server instantiation reflect the new version.	.github/workflows/release-please.yml .github/release-please-config.json packages/mcp/package.json packages/mcp/src/index.ts version.txt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.