Skip to content

Conversation

@jhaynie
Copy link
Member

@jhaynie jhaynie commented Jan 1, 2026

@coderabbitai pause

Summary by CodeRabbit

  • Chores
    • Version bump across all packages and apps (0.0.108 → 0.0.109).

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

@coderabbitai
Copy link

coderabbitai bot commented Jan 1, 2026

Note

Reviews paused

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.
📝 Walkthrough

Walkthrough

This pull request updates the version number from 0.0.108 to 0.0.109 across all package.json files in the monorepo, including the root package and all individual app and package manifests.

Changes

Cohort / File(s) Change Summary
Root and App Packages
package.json, apps/create-agentuity/package.json, apps/testing/package.json
Version bumped from 0.0.108 to 0.0.109
Core Packages
packages/auth/package.json, packages/cli/package.json, packages/core/package.json, packages/schema/package.json
Version bumped from 0.0.108 to 0.0.109
Feature Packages
packages/evals/package.json, packages/frontend/package.json, packages/react/package.json, packages/runtime/package.json
Version bumped from 0.0.108 to 0.0.109
Utility and Tool Packages
packages/server/package.json, packages/test-utils/package.json, packages/vscode/package.json, packages/workbench/package.json
Version bumped from 0.0.108 to 0.0.109

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • Release 0.0.106 #367: Performs identical version field updates across the same set of package.json files.
  • Release 0.0.108 #381: Similar release process that bumps version fields across all package.json manifests in the repo.
  • Release 0.0.107 #375: Prior version bump PR with the same pattern of updating the "version" field across all packages.

Pre-merge checks and finishing touches

✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release/0.0.109

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

@jhaynie jhaynie enabled auto-merge (squash) January 1, 2026 06:59
@jhaynie
Copy link
Member Author

jhaynie commented Jan 1, 2026

@coderabbitai pause

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
packages/evals/package.json (1)

32-32: Consider pinning dependency versions for reproducible builds.

Using "latest" for dependencies can lead to non-deterministic builds and unexpected breaking changes. While this is more critical for runtime dependencies like @ai-sdk/groq (line 32), it also applies to dev dependencies (lines 37-38).

Consider pinning to specific versions or using range specifiers like ^ to ensure build reproducibility.

Also applies to: 37-38

packages/runtime/package.json (1)

54-54: Consider pinning dev dependency versions.

Using "latest" for dev dependencies (lines 54, 58) can lead to non-deterministic builds. While less critical than runtime dependencies, pinning versions improves build reproducibility.

Also applies to: 58-58

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f6b2780 and 61d7fce.

⛔ Files ignored due to path filters (2)
  • apps/testing/e2e-web/src/generated/app.ts is excluded by !**/generated/**
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (15)
  • apps/create-agentuity/package.json
  • apps/testing/package.json
  • package.json
  • packages/auth/package.json
  • packages/cli/package.json
  • packages/core/package.json
  • packages/evals/package.json
  • packages/frontend/package.json
  • packages/react/package.json
  • packages/runtime/package.json
  • packages/schema/package.json
  • packages/server/package.json
  • packages/test-utils/package.json
  • packages/vscode/package.json
  • packages/workbench/package.json
🧰 Additional context used
📓 Path-based instructions (4)
**/*.{ts,tsx,js,jsx,json}

📄 CodeRabbit inference engine (AGENTS.md)

Use Prettier for code formatting with tabs (width 3), single quotes, and semicolons

Files:

  • packages/frontend/package.json
  • packages/server/package.json
  • package.json
  • apps/create-agentuity/package.json
  • packages/schema/package.json
  • packages/react/package.json
  • packages/evals/package.json
  • packages/test-utils/package.json
  • packages/auth/package.json
  • packages/cli/package.json
  • packages/workbench/package.json
  • packages/runtime/package.json
  • packages/core/package.json
  • packages/vscode/package.json
  • apps/testing/package.json
packages/react/**/package.json

📄 CodeRabbit inference engine (packages/react/AGENTS.md)

Peer dependencies must include React 18+ or 19+

Files:

  • packages/react/package.json
packages/test-utils/**/package.json

📄 CodeRabbit inference engine (packages/test-utils/AGENTS.md)

packages/test-utils/**/package.json: Ensure "private": true is set in package.json to prevent accidental npm publishing
List devDependencies with "@agentuity/test-utils": "workspace:*" format for workspace imports
Use only @agentuity/core and bun-types as dependencies to minimize dependency footprint

Files:

  • packages/test-utils/package.json
packages/core/**/package.json

📄 CodeRabbit inference engine (packages/core/AGENTS.md)

No runtime dependencies - keep this package lean with zero external dependencies

Files:

  • packages/core/package.json
🔇 Additional comments (18)
packages/schema/package.json (1)

3-3: LGTM! Version bump looks good.

The version increment to 0.0.109 is consistent with the release objective.

packages/test-utils/package.json (1)

3-3: LGTM! Version bump and package configuration are correct.

The version increment to 0.0.109 is appropriate. The package correctly maintains "private": true (line 5), uses workspace:* format for internal dependencies (line 14), and adheres to the minimal dependency footprint guideline with only @agentuity/core and bun-types.

packages/frontend/package.json (1)

3-3: LGTM! Version bump is consistent.

The version update to 0.0.109 aligns with the repository-wide release.

packages/workbench/package.json (1)

3-3: LGTM! Version bump is correct.

The version update to 0.0.109 is consistent with the monorepo-wide release.

package.json (1)

3-3: LGTM! Root version bump is consistent.

The monorepo root version update to 0.0.109 correctly matches all package versions in the workspace.

apps/create-agentuity/package.json (1)

3-3: Version bump looks good.

Clean version update from 0.0.108 to 0.0.109 with no other changes.

apps/testing/package.json (1)

3-3: Version bump looks good.

Straightforward version update to 0.0.109 aligned with the release.

packages/auth/package.json (1)

3-3: Version bump looks good.

Version incremented to 0.0.109 with no changes to dependencies, exports, or configuration.

packages/server/package.json (1)

3-3: LGTM - Version bump is correct.

The version update from 0.0.108 to 0.0.109 is consistent with the release objective.

packages/cli/package.json (1)

3-3: LGTM - Version bump is correct.

The version update aligns with the release objective.

packages/core/package.json (2)

3-3: LGTM - Version bump is correct.

The version update is consistent with the release objective.


31-32: Verify runtime dependency compliance with coding guidelines.

The coding guidelines specify that packages/core/**/package.json should have "No runtime dependencies - keep this package lean with zero external dependencies." However, zod is listed as a runtime dependency.

Please confirm whether this is an intentional exception or if the guideline needs updating.

As per coding guidelines, the core package should maintain zero external dependencies.

packages/vscode/package.json (1)

5-5: LGTM - Version bump is correct.

The version update is consistent with the release objective.

packages/react/package.json (2)

3-3: LGTM - Version bump is correct.

The version update aligns with the release objective.


39-41: Verify React peer dependency range against coding guidelines.

The coding guidelines specify that peer dependencies "must include React 18+ or 19+." The current configuration specifies ^19.0.0, which only supports React 19 and above, excluding React 18.

Consider whether the peer dependency should be broadened to support both React 18 and 19, for example: "react": "^18.0.0 || ^19.0.0".

As per coding guidelines, the React package should support React 18+ or 19+.

packages/evals/package.json (1)

3-3: LGTM: Version bump is consistent with the release.

The version update to 0.0.109 aligns correctly with the PR objective and maintains consistency across the monorepo.

packages/runtime/package.json (2)

3-3: LGTM: Version bump is consistent with the release.

The version update to 0.0.109 aligns correctly with the PR objective and maintains consistency across the monorepo.


50-50: Zod version 4.1.12 is valid and is the latest stable version.

The specified version exists and is stable as of January 2026.

@coderabbitai
Copy link

coderabbitai bot commented Jan 1, 2026

✅ Actions performed

Reviews paused.

@jhaynie jhaynie merged commit eb64748 into main Jan 1, 2026
9 checks passed
@jhaynie jhaynie deleted the release/0.0.109 branch January 1, 2026 07:02
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.

2 participants