chore(release): 1.2.11

[tonychang04]

Summary

Version bump only — cuts a release for the client=mcp tracking change merged in #56 so PostHog/Mixpanel can break down agent-connected events by source once users upgrade.

Files changed

• package.json 1.2.10 → 1.2.11
• package-lock.json 1.2.10 → 1.2.11
• server.json 1.2.6 → 1.2.11 (was stale, MCP Registry publish step needs this updated)

Test plan

• CI passes
• After merge, manually trigger publish-mcp.yml workflow
• Verify npm view @insforge/mcp version returns 1.2.11
• After a few days of upgrades, verify PostHog agent_connected events show non-zero client=mcp count

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated package version to 1.2.11 across manifest files.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0e0ff85e-880a-4492-aab3-f16070f8c7ed

📥 Commits

Reviewing files that changed from the base of the PR and between 649b586 and 0fe4476.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• package.json
• server.json

---

Walkthrough

This PR updates version numbers across configuration files from 1.2.10 to 1.2.11 in package.json and from 1.2.6 to 1.2.11 in server.json, affecting both the top-level manifest version and the npm package entry version.

Changes

Cohort / File(s)	Summary
Version Bump package.json	Updated @insforge/mcp package version from 1.2.10 to 1.2.11.
Version Bump server.json	Updated MCP server manifest version from 1.2.6 to 1.2.11 in both top-level "version" field and npm package entry.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• PR #52: Updates package.json version of @insforge/mcp as a consecutive release bump following this version increment.
• PR #34: Previously modified the same server.json version fields that are updated here, establishing the baseline for this version change.

Suggested reviewers

• jwfing
• Fermionic-Lyu

Poem

🐰 A hop and a bump, version's on the rise,
From 1.2.10, we claim the prize!
Server and package, now unified at 1.2.11,
Our manifests dance—this release is heaven! ✨

🚥 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 'chore(release): 1.2.11' directly and clearly indicates this is a version bump release commit, matching the actual changes which are exclusively version updates across package.json and server.json.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-1.2.11

---

_{Review rate limit: 4/5 reviews remaining, refill in 12 minutes.}

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