chore: Bump package versions to 0.4.0 across all packages

[gabrypavanello]

• Updated version numbers in package.json files for all packages to 0.4.0.
• Adjusted dependency specifications to reflect the new versioning.
• Ensured consistency across the monorepo with the latest version updates.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Summary by CodeRabbit

Release Notes

• Chores
  • Updated all package versions to 0.4.0 and aligned internal package dependencies to match.

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

Walkthrough

Coordinated version bump across seven package.json files from 0.3.0 to 0.4.0, with corresponding dependency version updates in ui-react-builder and ui-react packages to maintain internal dependency consistency.

Changes

Cohort / File(s)	Summary
Core packages version bump package.json, packages/core/package.json, packages/create-app/package.json, packages/testing/package.json, packages/ui/package.json	Version updated from 0.3.0 to 0.4.0
ui-react-builder packages/ui-react-builder/package.json	Version bumped from 0.3.0 to 0.4.0; peerDependencies updated to require @mcp-apps-kit/core^0.4.0 and @mcp-apps-kit/ui-react^0.4.0
ui-react packages/ui-react/package.json	Version bumped from 0.3.0 to 0.4.0; dependency @mcp-apps-kit/ui updated from ^0.3.0 to ^0.4.0

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• chore: Bump package versions to 0.3.0 across all packages and update dependencies #70: Performs coordinated version bumps and peerDependencies/dependency updates in the same package.json files
• Bump patch version for release #50: Performs package.json version bumps across the same packages (core, create-app, ui, ui-react)
• chore: update package versions to 0.2.0 across core, create-app, ui-react, and ui packages #45: Performs package.json version bumps across the same packages with inter-package dependency version updates

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d6d004c and c0a1d66.

📒 Files selected for processing (7)

• package.json
• packages/core/package.json
• packages/create-app/package.json
• packages/testing/package.json
• packages/ui-react-builder/package.json
• packages/ui-react/package.json
• packages/ui/package.json

---

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

[claude]

Code Review Summary

This PR bumps the package versions from 0.3.0 to 0.4.0 across the monorepo. Overall, the changes are clean and consistent. Here's my detailed review:

✅ Positive Aspects

1. Consistency: All 7 package.json files are updated uniformly
2. Dependency Alignment: Internal peerDependencies correctly updated (e.g., ui-react-builder → core and ui-react)
3. Monorepo Coordination: Both workspace packages and root package.json are synchronized
4. Clean Diff: Simple version bump without unrelated changes

🔍 Observations & Recommendations

1. Release Process Alignment ⚠️

The PR description mentions this is a version bump, but I noticed the repo has automated release scripts in package.json:

• release:version:patch
• release:version:minor
• release:version:major

Question: Was this PR generated by running one of these scripts, or was it a manual bump?

• If manual: Consider using the automated scripts going forward for consistency
• If automated: The Nx release command should have handled this (looks good!)

2. Missing CHANGELOG ℹ️

I couldn't find a CHANGELOG.md file in the repository. For a 0.3.0 → 0.4.0 minor version bump, it would be helpful to document:

• What new features/breaking changes warrant a minor version bump
• Migration guide if there are breaking changes
• Notable fixes or improvements

Recommendation: Consider adding a CHANGELOG.md at the root level following Keep a Changelog format.

3. Version Bump Type 📊

This is a minor version bump (0.3.0 → 0.4.0). According to semantic versioning:

• Minor = new features, backwards-compatible
• Patch = bug fixes only
• Major = breaking changes

Verification needed: Does this release include new features? If it's primarily bug fixes, a patch bump (0.3.1) might be more appropriate.

4. Git Tags & Releases 🏷️

After merging, ensure to:

• Create a git tag: git tag v0.4.0
• Push the tag: git push origin v0.4.0
• Create a GitHub Release with release notes

📋 Checklist Before Merge

• Verify this is the correct version bump type (minor vs patch)
• Add CHANGELOG.md entries if not already present
• Run pnpm build && pnpm test && pnpm lint && pnpm typecheck (per CLAUDE.md)
• After merge: create git tag and GitHub release
• After merge: publish to npm with npm publish for each package

Code Quality: ✅ APPROVED

No code quality issues, security concerns, or bugs detected. The changes are purely version number updates with correct internal dependency alignment.

Test Coverage

No test changes needed for version bumps. Existing test suites will validate the packages work correctly at the new version.

---

Overall Assessment: This is a clean version bump PR. Main suggestion is to enhance the release process with CHANGELOG documentation and verify the version bump type aligns with the changes being released.