Bump SDK version to v0.1.0

[peteski22]

Summary by CodeRabbit

• Chores
  • Version updated to 0.1.0

---

Note: This release does not include user-facing features or bug fixes. It represents a minor version update for administrative purposes. No functional changes have been made to the application.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The package version in package.json has been incremented from 0.0.4 to 0.1.0. This is a minor version bump with no changes to functional code, control flow, or other metadata fields.

Changes

Cohort / File(s)	Summary
Version bump package.json	Version field updated from 0.0.4 to 0.1.0

Possibly related PRs

• Bump version to 0.0.3 #16: Makes the same type of change—updating the package.json "version" field for release versioning.
• Bump release to v0.0.4 #21: Directly modifies the same file and field with related version bumps (0.0.3→0.0.4 previously, 0.0.4→0.1.0 in this PR).

Suggested reviewers

• agpituk
• HareeshBahuleyan

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating the package version from 0.0.4 to 0.1.0 in package.json.
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.}

---

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 and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @package.json:
- Line 3: Create a CHANGELOG.md documenting the v0.1.0 release referenced by the
"version": "0.1.0" bump in package.json; include a clear header for v0.1.0, list
new features, bug fixes, and any breaking changes or migration steps since
v0.0.4, add dates and contributor/PR references where applicable, and commit the
changelog alongside the package.json version bump so users can see what changed
and how to upgrade.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c5cadde and e14126d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for release documentation and version history

echo "=== Looking for CHANGELOG/release files ==="
fd -i 'changelog|history|releases' -e md -e txt 2>/dev/null | head -20

echo -e "\n=== Checking docs directory ==="
fd -t f . docs/ -e md 2>/dev/null | head -20

echo -e "\n=== Searching for v0.1.0 or 0.1.0 mentions ==="
rg -i '0\.1\.0|v0\.1\.0' -g "*.md" -g "*.txt" 2>/dev/null | head -30

echo -e "\n=== Checking git history for recent commits ==="
git log --oneline -20 2>/dev/null || echo "Git history not available"

echo -e "\n=== Listing root directory files ==="
ls -la | grep -E '\.(md|txt)$'

Repository: mozilla-ai/mcpd-sdk-javascript

Length of output: 581

---

Add release documentation for v0.1.0.

No CHANGELOG or release notes exist in the repository to document what is included in v0.1.0. Before or alongside this version bump, create a CHANGELOG.md (or similar) detailing the changes, new features, and any breaking changes since v0.0.4. This ensures users understand what is included in this release and any migration steps needed when upgrading.

🤖 Prompt for AI Agents

In @package.json at line 3, Create a CHANGELOG.md documenting the v0.1.0 release
referenced by the "version": "0.1.0" bump in package.json; include a clear
header for v0.1.0, list new features, bug fixes, and any breaking changes or
migration steps since v0.0.4, add dates and contributor/PR references where
applicable, and commit the changelog alongside the package.json version bump so
users can see what changed and how to upgrade.