chore: version bump to 2.5.0 - #225
Conversation
Bumps VERSION to 2.5.0 for the first release carrying the Claude Desktop extension (.mcpb) pipeline (#224). Refreshes generated version references and stats (CLAUDE.md, README stats, llms.txt, llms-full.txt, site stats, testing docs). Claude-Session: https://claude.ai/code/session_01LJ6D4L6rnms9GqMqqc2tFb
Reviewer's GuideMinor release prep PR that bumps the semantic version to 2.5.0 and regenerates all derived statistics and docs (testing, README, site, LLM lists) to reflect the new tests and MCP bundle pipeline, plus updating project documentation to include the new mcpb/ directory and extension details. Flow diagram for v2_5_0 release pipeline including mcpb bundleflowchart LR
Tag["Git tag v2.5.0 pushed"] --> CI["CI E2E gate pipeline"]
CI --> GoReleaser["GoReleaser release (darwin_universal binary)"]
GoReleaser --> MCPB["scripts/build-mcpb.sh (build .mcpb bundle)"]
GoReleaser --> Docker["Docker image build and publish"]
MCPB --> MCPRegistry["MCP Registry publish"]
MCPRegistry --> Manifest["Manifest commit-back"]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Warning Review limit reached
Next review available in: 40 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Code Review
This pull request bumps the project version from 2.4.1 to 2.5.0 across several files, including CLAUDE.md, VERSION, llms.txt, and site/src/data/stats.json. It also updates various code, testing, and coverage statistics in README.md and docs/development/testing/testing.md, and documents the addition of the mcpb/ directory. There are no review comments, and I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull request overview
This PR prepares the v2.5.0 release by bumping the repository version and updating regenerated documentation/statistics artifacts that are published/consumed by users (README stats, site stats, and LLM reference files).
Changes:
- Bumped the canonical
VERSIONto2.5.0and propagated it into site/docs artifacts. - Refreshed generated metrics in
README.mdanddocs/development/testing/testing.md. - Updated LLM discovery/reference artifacts (
llms.txt,llms-full.txt) for the new release.
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| VERSION | Version bump to 2.5.0 (release tag source of truth). |
| site/src/data/stats.json | Site-consumed stats updated to version 2.5.0. |
| README.md | Regenerated repository “Unnecessary statistics” block. |
| llms.txt | Updated LLM discovery summary version string. |
| llms-full.txt | Updated full reference header version string (resource-count inconsistency noted). |
| docs/development/testing/testing.md | Regenerated testing metrics and coverage tables. |
| CLAUDE.md | Updated version table and project tree to include mcpb/. |
| # gitlab-mcp-server — Full Reference | ||
|
|
||
| > Version 2.4.1 | up to 1071 tools | 32 base meta-tools; 49 self-managed enterprise meta-tools; 50 GitLab.com Enterprise meta-tools | 2 dynamic tools | 46 resources | 37 prompts | ||
| > Version 2.5.0 | up to 1071 tools | 32 base meta-tools; 49 self-managed enterprise meta-tools; 50 GitLab.com Enterprise meta-tools | 2 dynamic tools | 46 resources | 37 prompts |
|
## Description Bump the patch version **2.5.0 → 2.5.1** and update every reference that tracks it. ## Related Issue N/A ## Type of Change - [x] CI / build / tooling ## Changes Made - `VERSION` 2.5.0 → 2.5.1 (single source of truth) - `CLAUDE.md` — version table row + `VERSION` comment - Regenerated version-tracking artifacts: - `README.md` (stats section) - `llms.txt` / `llms-full.txt` - `docs/development/testing/testing.md` - `site/src/data/stats.json` ## Not touched (by design) `server.json`, `mcpb/manifest.json`, and `.plugin/plugin.json` carry the version + download URLs + SHAs stamped by the **release automation** (`scripts/update-server-json-sha.sh`) at tag time. Prior version-bump PRs (e.g. #225) leave them for the release, and `check-server-json` validates the schema, not the version string. ## How to Test ```bash cat VERSION # 2.5.1 go run ./cmd/gen_stats/ --check # passes go run ./cmd/gen_llms/ --check # passes go run ./cmd/format_md_tables/ --check # passes ``` ## Breaking Changes / Migration Notes N/A ## Checklist - [x] `VERSION` bumped (single source of truth) - [x] All version-tracking files regenerated and consistent - [x] `check-stats`, `check-llms`, `check-md-tables` pass - [x] Release-stamped manifests left for release automation (per convention) <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/jmrplens/gitlab-mcp-server/pull/240?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. -->



Bumps
VERSIONto 2.5.0 — first release carrying the Claude Desktop extension (.mcpb) pipeline (#224).VERSION2.4.1 → 2.5.0 (minor: new feature)CLAUDE.md: version table + project tree (addsmcpb/)llms.txt/llms-full.txt, site stats, testing docs (make update-all)After merging, tagging the squash commit as
v2.5.0triggers the release pipeline (E2E gate → GoReleaser incl. darwin universal binary →.mcpbasset → Docker → MCP Registry → manifest commit-back).Release-pipeline changes were verified locally end to end: GoReleaser snapshot →
scripts/build-mcpb.sh→ stamped bundle unpacked, fat binary (x86_64+arm64) smoke-tested over stdio.https://claude.ai/code/session_01LJ6D4L6rnms9GqMqqc2tFb
Summary by Sourcery
Bump the project version to 2.5.0 and regenerate codebase and testing statistics for the release.
Documentation:
Tests:
Chores: