chore(main): release mcp-edd 1.2.0

[jack-arturo]

🤖 I have created a release beep boop

1.2.0 (2026-02-18)

Features

• V2 API support, new tools, and API docs (#21) (44faa6d)

Bug Fixes

• sync server.json package version with npm (1.1.0) (#19) (27e73bb)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Summary by CodeRabbit

• New Features
  • Introduces v1.2.0 with V2 API support, new tooling, and updated API documentation.
• Documentation
  • Adds a 1.2.0 changelog entry detailing features and fixes.
• Bug Fixes
  • Resolved version synchronization inconsistencies across release artifacts.

Walkthrough

This pull request releases version 1.2.0 with a version bump applied across manifest and configuration files and adds a 1.2.0 entry to CHANGELOG.md documenting features and a bug fix.

Changes

Cohort / File(s)	Summary
Version Bumps .release-please-manifest.json, manifest.json, package.json, server.json	Top-level version values updated from 1.1.0 to 1.2.0.
Changelog CHANGELOG.md	Added a 1.2.0 release entry (Features and Bug Fixes); existing 1.1.0 section unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Add MCP extension files and update docs #6 — touches manifest.json and package.json (related to version/package metadata changes).

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: a release version bump from 1.1.0 to 1.2.0 for the mcp-edd package.
Description check	✅ Passed	The description is clearly related to the changeset, documenting the release with version bump, features, and bug fixes that align with the file changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-please--branches--main--components--mcp-edd

---

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

server.json (1)

12-21: ⚠️ Potential issue | 🔴 Critical

Critical: Nested package version is out of sync.

The packages[0].version at line 16 is still "1.1.0" while the top-level version at line 6 has been updated to "1.1.1". This creates the same inconsistency that the changelog indicates was fixed in this release ("sync server.json package version with npm").

This version mismatch can cause confusion for package managers and registries, as the server metadata claims version 1.1.1 but references package version 1.1.0.

🔧 Proposed fix to sync the package version

   "packages": [
     {
       "registryType": "npm",
       "identifier": "@verygoodplugins/mcp-edd",
-      "version": "1.1.0",
+      "version": "1.1.1",
       "transport": {
         "type": "stdio"
       }
     }
   ],

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@server.json` around lines 12 - 21, Update the nested package version so it
matches the top-level "version" value: change packages[0].version from "1.1.0"
to "1.1.1" (ensure the field referenced is packages[0].version in server.json so
the nested package entry stays in sync with the top-level version).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@server.json`:
- Around line 12-21: Update the nested package version so it matches the
top-level "version" value: change packages[0].version from "1.1.0" to "1.1.1"
(ensure the field referenced is packages[0].version in server.json so the nested
package entry stays in sync with the top-level version).