Release/bump version 0.1.3

[peteski22]

Summary by CodeRabbit

Release Notes

• Chores
  • Version updated to 0.1.3

[coderabbitai]

Warning

Review limit reached

@peteski22, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 57 minutes and 49 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 647da8ad-daf1-4f52-a76b-c7f5b81d87ed

📥 Commits

Reviewing files that changed from the base of the PR and between 5e4cf44 and 47fecc9.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json

Walkthrough

The PR updates the npm package version from 0.1.2 to 0.1.3 in package.json. No dependencies, scripts, or other package metadata fields are modified.

Changes

Package Version Update

Layer / File(s)	Summary
Version bump to 0.1.3 package.json	The npm package version field is incremented from 0.1.2 to 0.1.3.

Possibly related PRs

• mozilla-ai/mcpd-sdk-javascript#16: Both PRs update only the version field in package.json with no other code-level changes.
• mozilla-ai/mcpd-sdk-javascript#31: Both PRs update only the version field in package.json with no other code-level changes.
• mozilla-ai/mcpd-sdk-javascript#40: Both PRs update only the version field in package.json with no other code-level changes.

Suggested reviewers

• dpoulopoulos

🚥 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 accurately describes the main change in the pull request, which is bumping the package version from 0.1.2 to 0.1.3.
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 release/bump-version-0.1.3

---

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

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 3: package.json's "version" value was updated to 0.1.3 but the
corresponding package-lock.json files (root package-lock.json and
examples/vercel-ai/package-lock.json and examples/langchain/package-lock.json)
still show 0.1.2; regenerate and commit those lockfiles by running npm install
(or npm ci) in the root and in each example directory to update their
package-lock.json files so they reflect version 0.1.3, then add and commit the
updated lockfiles alongside the package.json change.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d474bbd0-7df8-4ad7-a1a0-603c949df17b

📥 Commits

Reviewing files that changed from the base of the PR and between d83761c and 5e4cf44.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json