chore(main): release sdk-v 0.3.0

[github-actions]

🤖 I have created a release beepboop

0.3.0 (2026-05-29)

Features

• update MCP SDK and monitoring (#227) (4be5b33)

---

This PR was generated with Release Please. See documentation.

Greptile Summary

Automated Release Please PR bumping @terminal49/sdk from 0.2.0 to 0.3.0. The underlying feature (MCP SDK and monitoring update from PR #227) was already merged; this PR only carries the version and changelog bookkeeping.

• package.json and package-lock.json version fields updated to 0.3.0 with no dependency changes.
• CHANGELOG.md and .release-please-manifest.json updated to reflect the new version.

Confidence Score: 5/5

Safe to merge — all changes are version number updates generated automatically by Release Please with no logic or dependency modifications.

Every changed line is a mechanical version string update (0.2.0 → 0.3.0) across four files. The actual feature work landed in a prior PR; this PR carries no new code paths, no dependency changes, and no configuration changes that could introduce regressions.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 0.2.0 to 0.3.0 for the typescript-sdk package — standard Release Please manifest update.
sdks/typescript-sdk/CHANGELOG.md	0.3.0 changelog entry added, noting the MCP SDK and monitoring update from PR #227.
sdks/typescript-sdk/package.json	Package version bumped from 0.2.0 to 0.3.0; no dependency changes.
sdks/typescript-sdk/package-lock.json	Lockfile version bumped in both the root and the package entry to match the new 0.3.0 version.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["PR #227 merged\n(MCP SDK & monitoring update)"] --> B["Release Please bot\ndetects feat commit"]
B --> C["Generates release PR #232"]
C --> D["Bumps version: 0.2.0 → 0.3.0"]
D --> E[".release-please-manifest.json"]
D --> F["sdks/typescript-sdk/package.json"]
D --> G["sdks/typescript-sdk/package-lock.json"]
D --> H["sdks/typescript-sdk/CHANGELOG.md"]
E & F & G & H --> I["Merge → publish @terminal49/sdk@0.3.0"]

Loading

_{Reviews (1): Last reviewed commit: "chore(main): release sdk-v 0.3.0" | Re-trigger Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api	Ready	Preview, Comment	May 29, 2026 11:57pm

[dodeja]

@claude fix this

[claude]

Claude finished @dodeja's task in 2m 18s —— View job

---

Fix applied

Root cause: Release Please bumped @terminal49/sdk to 0.3.0 in the SDK's own files, but left stale 0.2.0 references in the MCP package and root lockfile. This caused npm ci to fail on Vercel due to a version mismatch.

Changes pushed (commit d80b1e0):

• packages/mcp/package.json — bumped @terminal49/sdk dependency 0.2.0 → 0.3.0

• package-lock.json — updated two stale 0.2.0 entries (MCP dependency + SDK workspace version) to 0.3.0

• Gather context and identify root cause

• Update packages/mcp/package.json — bump @terminal49/sdk dep to 0.3.0

• Update root package-lock.json — fix stale 0.2.0 version references

• Commit and push fix

Vercel should re-deploy with a clean npm ci now.

[github-actions]

🤖 Created releases:

• sdk-v-v0.3.0

🌻