Skip to content

chore: bump package versions to 0.5.0 across all packages - #99

Merged
gabrypavanello merged 1 commit into
mainfrom
bump-0.5.0
Jan 14, 2026
Merged

chore: bump package versions to 0.5.0 across all packages#99
gabrypavanello merged 1 commit into
mainfrom
bump-0.5.0

Conversation

@gabrypavanello

Copy link
Copy Markdown
Contributor

Updated the version of all packages in the monorepo from 0.4.0 to 0.5.0, ensuring consistency across the project. This includes updates in package.json files for core, create-app, testing, ui, ui-react, ui-react-builder, and their respective dependencies in pnpm-lock.yaml.

Updated the version of all packages in the monorepo from 0.4.0 to 0.5.0, ensuring consistency across the project. This includes updates in package.json files for core, create-app, testing, ui, ui-react, ui-react-builder, and their respective dependencies in pnpm-lock.yaml.
@coderabbitai

coderabbitai Bot commented Jan 14, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Version 0.5.0 released across the entire package suite with synchronized version updates and dependency alignments.

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

Walkthrough

This PR performs a coordinated version bump from 0.4.0 to 0.5.0 across all packages in the monorepo, including updates to internal package dependencies referencing the previous version. No functional or control-flow changes are made.

Changes

Cohort / File(s) Summary
Root and core packages
package.json, packages/core/package.json, packages/create-app/package.json, packages/testing/package.json, packages/ui/package.json
Version bumped from 0.4.0 to 0.5.0
UI and React packages with dependency updates
packages/ui-react/package.json
Version bumped from 0.4.0 to 0.5.0; @mcp-apps-kit/ui dependency updated from ^0.4.0 to ^0.5.0
UI React Builder
packages/ui-react-builder/package.json
Version bumped from 0.4.0 to 0.5.0; @mcp-apps-kit/core and @mcp-apps-kit/ui-react dependencies updated from ^0.4.0 to ^0.5.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main changeset: bumping package versions to 0.5.0 across all packages in the monorepo.
Description check ✅ Passed The description clearly relates to the changeset, detailing the version bumps across specific packages and mentioning updates to both package.json and lock files.
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.



📜 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 0fa55cc and 221c20d.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 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
🧰 Additional context used
🧠 Learnings (10)
📓 Common learnings
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/create-app/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:19.638Z
Learning: Applies to packages/create-app/**/*.{ts,tsx,js} : Verify that package versions fetched from npm registry at runtime are valid before generating projects in mcp-apps-kit/create-app
📚 Learning: 2026-01-11T17:08:19.638Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/create-app/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:19.638Z
Learning: Applies to packages/create-app/**/*.{ts,tsx,js} : Verify that package versions fetched from npm registry at runtime are valid before generating projects in mcp-apps-kit/create-app

Applied to files:

  • packages/ui/package.json
  • package.json
  • packages/core/package.json
  • packages/create-app/package.json
  • packages/ui-react-builder/package.json
  • packages/testing/package.json
  • packages/ui-react/package.json
📚 Learning: 2026-01-11T17:08:30.346Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/ui-react-builder/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:30.346Z
Learning: Ensure the vite peer dependency is installed when using the mcp-apps-kit/ui-react-builder/vite plugin

Applied to files:

  • packages/ui/package.json
  • packages/ui-react-builder/package.json
  • packages/ui-react/package.json
📚 Learning: 2026-01-11T17:08:42.176Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/ui/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:42.176Z
Learning: Applies to packages/ui/**/*.{ts,tsx,js,jsx} : Handle both MCP and OpenAI response formats when calling tools

Applied to files:

  • packages/ui/package.json
  • packages/ui-react-builder/package.json
  • packages/ui-react/package.json
📚 Learning: 2026-01-11T17:08:19.638Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/create-app/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:19.638Z
Learning: Applies to packages/create-app/**/*.{ts,tsx,js} : Generate projects using npm (not pnpm) to avoid workspace conflicts in mcp-apps-kit/create-app scaffolded projects

Applied to files:

  • package.json
  • packages/create-app/package.json
  • packages/ui-react-builder/package.json
📚 Learning: 2026-01-11T17:08:19.638Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/create-app/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:19.638Z
Learning: Applies to packages/create-app/**/*.{ts,tsx,js} : Use path.join() instead of string concatenation for cross-platform file path operations in the mcp-apps-kit/create-app scaffolding tool

Applied to files:

  • packages/create-app/package.json
  • packages/ui-react-builder/package.json
📚 Learning: 2026-01-11T17:08:30.346Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/ui-react-builder/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:30.346Z
Learning: Applies to packages/ui-react-builder/**/*.tsx : Use .tsx extension for files containing JSX and ensure jsx: 'automatic' is configured in esbuild settings

Applied to files:

  • packages/ui-react-builder/package.json
  • packages/ui-react/package.json
📚 Learning: 2026-01-11T17:08:36.676Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/ui-react/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:36.676Z
Learning: Applies to packages/ui-react/**/*.{tsx,jsx} : Ensure components using MCP hooks (`useAppsClient`, `useToolResult`, `useHostContext`, `useDocumentTheme`, `useHostStyleVariables`) are rendered within an `AppsProvider` context wrapper

Applied to files:

  • packages/ui-react-builder/package.json
  • packages/ui-react/package.json
📚 Learning: 2026-01-11T17:08:36.676Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/ui-react/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:36.676Z
Learning: Applies to packages/ui-react/**/*.{tsx,jsx} : Wrap your React application with `AppsProvider` context provider to enable access to MCP client and host context

Applied to files:

  • packages/ui-react-builder/package.json
  • packages/ui-react/package.json
📚 Learning: 2026-01-11T17:08:36.676Z
Learnt from: CR
Repo: AndurilCode/mcp-apps-kit PR: 0
File: packages/ui-react/AGENTS.md:0-0
Timestamp: 2026-01-11T17:08:36.676Z
Learning: Applies to packages/ui-react/**/*.{tsx,jsx} : Use `useDocumentTheme()` and `useHostStyleVariables()` hooks to automatically apply theming based on host context (theme and locale)

Applied to files:

  • packages/ui-react/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: test-and-lint
🔇 Additional comments (7)
packages/core/package.json (1)

3-3: LGTM!

Version bump to 0.5.0 is consistent with the PR objective. No internal dependencies require updating in this package.

package.json (1)

3-3: LGTM!

Root monorepo version bump to 0.5.0 aligns with the coordinated release across all packages.

packages/create-app/package.json (1)

3-3: LGTM!

Version bump to 0.5.0 is correct. This CLI package has no internal @mcp-apps-kit dependencies that need updating.

packages/ui/package.json (1)

3-3: LGTM!

Version bump to 0.5.0 is consistent. This package has no internal dependencies requiring updates.

packages/ui-react-builder/package.json (1)

3-3: LGTM!

Version bump to 0.5.0 and corresponding peer dependency updates for @mcp-apps-kit/core and @mcp-apps-kit/ui-react are correctly aligned. The workspace:* specifiers in devDependencies appropriately reference local packages for development.

Also applies to: 58-59

packages/testing/package.json (1)

3-3: LGTM!

Version bump to 0.5.0 is consistent with the monorepo-wide version update. No internal dependencies require updating in this package.

packages/ui-react/package.json (1)

3-3: LGTM!

Version bump to 0.5.0 and the corresponding internal dependency update for @mcp-apps-kit/ui are correctly synchronized. This ensures version consistency across the monorepo.

Also applies to: 47-47

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.


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

@claude

claude Bot commented Jan 14, 2026

Copy link
Copy Markdown
Contributor

Code Review - PR #99

Summary

This PR bumps all package versions from 0.4.0 to 0.5.0 across the monorepo. This is a minor version bump.

✅ Positive Findings

  1. Consistent Version Updates: All package versions were updated uniformly:

    • Root monorepo package
    • All 6 publishable packages (core, ui, ui-react, ui-react-builder, testing, create-app)
    • Internal dependencies (peerDependencies and dependencies)
    • pnpm-lock.yaml was properly updated
  2. Follows Project Conventions: The commit message follows the conventional commits format with chore: prefix, which is appropriate for version bumps.

  3. No Source Code Changes: The version bump is isolated to package.json files and lockfile, with no inadvertent code changes.

⚠️ Critical Issues

ISSUE #1: Release Script Not Used

According to CLAUDE.md:18, the project has standardized release scripts:

pnpm release:version:patch     # Also: minor, major

Looking at package.json:17, the proper command for a minor version bump is:

pnpm release:version:minor

This command:

  • Uses nx release version minor for coordinated versioning
  • Updates all packages in the correct order
  • Automatically updates the root package.json
  • Stages the changes with git add package.json

Manually editing version numbers bypasses the project's release workflow and increases the risk of inconsistencies.

📋 Pre-Merge Checklist

According to CLAUDE.md:5-9, all four of these must pass before merging:

pnpm build && pnpm test && pnpm lint && pnpm typecheck

Question for PR author: Have these checks been run? The PR description doesn't mention them.

🤔 Questions

  1. Why a minor version bump (0.4.0 → 0.5.0)?

    • What new features or backwards-compatible functionality was added?
    • If this is just keeping versions synchronized, should it be a patch bump instead?
    • Is there a CHANGELOG entry explaining what's new in 0.5.0?
  2. Was this manually created or generated by the release script?

    • If manual, it should be recreated using pnpm release:version:minor
    • If generated, the commit message suggests otherwise

💡 Recommendations

  1. Use the standardized release workflow: Close this PR and create a new one using:

    pnpm release:version:minor
    git commit -m "chore: release version 0.5.0"
  2. Document the release: Consider adding what's new in 0.5.0 to help users understand the changes.

  3. Verify CI passes: Ensure all required checks (build, test, lint, typecheck) pass before merging.

Verdict

While the version updates themselves are technically correct and consistent, the process doesn't follow the established project conventions. Using the standardized release script ensures:

  • Consistency across future releases
  • Reduced human error
  • Proper Nx coordination
  • Adherence to team conventions

Note: Code references

  • Release scripts: package.json:14-19
  • Project requirements: CLAUDE.md:5-9, CLAUDE.md:18

@gabrypavanello
gabrypavanello merged commit 152acee into main Jan 14, 2026
4 checks passed
@gabrypavanello
gabrypavanello deleted the bump-0.5.0 branch January 14, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant