chore(main): release 1.2.0

[github-actions]

🤖 I have created a release beep boop

1.2.0 (2026-04-15)

Features

• add mcpsandbox package to monorepo (b87dab8)
• expose just-bash runtime options (b9195c2)
• Introduce browser-only AI SDK client with a dedicated demo and shared MCP proxy logic. (255826e)

Bug Fixes

• Prevent Prism auto-highlighting conflicts in Features section, enhance FAQ hash-based scrolling to react to URL changes, and correct a typo. (a2a9ce4)

---

This PR was generated with Release Please. See documentation.

[mesa-dot-dev]

Mesa Description

TL;DR

Release version 1.2.0 with new browser-only AI SDK client and bug fixes for documentation site.

What changed?

• Added browser-only AI SDK client with dedicated demo application and shared MCP proxy logic
• Fixed Prism syntax highlighter conflicts in Features section
• Enhanced FAQ hash-based scrolling to properly respond to URL changes
• Corrected documentation typos
• Updated CHANGELOG.md and package.json to reflect 1.2.0 release

^{Description generated by Mesa. Update settings}

[mesa-dot-dev]

Performed full review of b0b9978...56876f1

Analysis

1. Misaligned Versioning Strategy: The root package version (v1.1.1) differs significantly from published workspace packages (v0.1.x), creating confusion about what versions mean and serving no functional purpose as the root isn't published.

2. Improper Monorepo Configuration: Release-please lacks proper monorepo configuration (missing manifest files), causing it to only track the root package while workspace packages are versioned manually with no coordination.

3. Documentation Changes Triggering Unnecessary Version Bumps: This PR bumps version for docs-only changes, creating misleading version numbers that suggest code/API changes when none exist.

4. Release Workflow Inconsistency: The release workflow publishes packages that weren't version-bumped by release-please, leading to version drift between root (1.1.x) and published packages (0.1.x).

5. Missing Private Flag: Root package.json isn't marked as private despite never being published to npm, creating ambiguity about its purpose in the versioning system.

Tip

Help

Slash Commands:

• /review - Request a full code review
• /review latest - Review only changes since the last review
• /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
• /help - Get help with Mesa commands and configuration options

^{2 files reviewed | 1 comments | Edit Agent Settings • Read Docs}

[mesa-dot-dev]

The changelog describes documentation-specific changes ("Prism auto-highlighting conflicts in Features section, enhance FAQ hash-based scrolling"), which only affect the docs/ directory that is marked as private: true. These changes shouldn't trigger a version bump on the root package that users might reference.

Consider separating documentation changes from release versioning, or implementing a conventional commit prefix like docs: that release-please can be configured to ignore for version bumps.

Agent: 🏛 Architecture • 

Prompt for Agent

Task: Address review feedback left on GitHub.
Repository: buremba/1mcp#6
File: CHANGELOG.md#L8
Action: Open this file location in your editor, inspect the highlighted code, and resolve the issue described below.

Feedback:
The changelog describes documentation-specific changes ("Prism auto-highlighting conflicts in Features section, enhance FAQ hash-based scrolling"), which only affect the `docs/` directory that is marked as `private: true`. These changes shouldn't trigger a version bump on the root package that users might reference.

Consider separating documentation changes from release versioning, or implementing a conventional commit prefix like `docs:` that release-please can be configured to ignore for version bumps.

[mesa-dot-dev]

Mesa Description

TL;DR

Release version 1.2.0 with new AI SDK browser client, mcpsandbox package addition, improved bash runtime options, and bug fixes for documentation site.

What changed?

• CHANGELOG.md: Updated with v1.2.0 release notes including three features (mcpsandbox package, bash runtime options, browser-only AI SDK) and one bug fix (Prism highlighting, FAQ scrolling, typo)
• package.json: Version bumped from 1.1.0 to 1.2.0

^{Description generated by Mesa. Update settings}

[mesa-dot-dev]

Mesa Description

TL;DR

Release version 1.2.0 with new browser-only AI SDK client, mcpsandbox package addition to monorepo, exposed bash runtime options, and bug fixes for documentation site.

What changed?

• CHANGELOG.md: Updated with release notes for v1.2.0 including features and bug fixes
• package.json: Version bumped from 1.1.0 to 1.2.0

^{Description generated by Mesa. Update settings}

[mesa-dot-dev]

Mesa Description

TL;DR

Release v1.2.0 with new browser-only AI SDK client, mcpsandbox package addition, runtime options exposure, and documentation fixes.

What changed?

• Added mcpsandbox package to monorepo
• Exposed just-bash runtime options for better configurability
• Introduced browser-only AI SDK client with dedicated demo and shared MCP proxy logic
• Fixed Prism auto-highlighting conflicts in Features section and enhanced FAQ hash-based scrolling
• Updated CHANGELOG.md and package.json to reflect v1.2.0 release

^{Description generated by Mesa. Update settings}