Skip to content

Release 0.0.97#210

Merged
jhaynie merged 1 commit into
mainfrom
release/0.0.97
Dec 17, 2025
Merged

Release 0.0.97#210
jhaynie merged 1 commit into
mainfrom
release/0.0.97

Conversation

@jhaynie
Copy link
Copy Markdown
Member

@jhaynie jhaynie commented Dec 17, 2025

Summary by CodeRabbit

  • Chores
    • Version bumped to 0.0.97 across all packages and applications.

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Dec 17, 2025

Walkthrough

A version bump across the entire monorepo, incrementing package versions from 0.0.96 to 0.0.97 in 13 package.json files spanning the root, apps, and packages directories. No functional, behavioral, or API changes.

Changes

Cohort / File(s) Summary
Root & App Packages
package.json, apps/create-agentuity/package.json, apps/testing/package.json
Version incremented from 0.0.96 to 0.0.97
Library Packages
packages/auth/package.json, packages/cli/package.json, packages/core/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
Version incremented from 0.0.96 to 0.0.97

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Homogeneous, repetitive version string updates across all package.json files
  • No functional, structural, or behavioral changes to review

Possibly related PRs

Poem

🐰 Hop, hop, hooray! The version rises high,
From ninety-six to ninety-seven we fly!
Each package.json tweaked with care,
A synchronized update everywhere! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Release 0.0.97' is fully related to the main change: updating all package.json files from version 0.0.96 to 0.0.97 across the entire monorepo.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ 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.97

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

Copy link
Copy Markdown
Contributor

@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/react/package.json (1)

36-38: Consider supporting React 18+ for backward compatibility.

The peerDependencies currently require React 19+ only. Based on coding guidelines, peer dependencies should include React 18+ or 19+. For broader compatibility, consider:

 "peerDependencies": {
-  "@types/react": "^19.0.0",
-  "react": "^19.0.0"
+  "@types/react": "^18.0.0 || ^19.0.0",
+  "react": "^18.0.0 || ^19.0.0"
 }

This pattern is already used correctly in packages/auth/package.json (Line 22). Based on coding guidelines.

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

26-26: Consider using workspace protocol for internal dependencies.

The dependency on @agentuity/cli uses "latest" instead of "workspace:*". While this might be intentional for a CLI wrapper, the coding guidelines recommend using the workspace protocol for cross-package imports within the monorepo to ensure consistency and proper versioning.

Based on coding guidelines, consider applying this diff:

-    "@agentuity/cli": "latest"
+    "@agentuity/cli": "workspace:*"

If the "latest" specifier is intentional (e.g., to always fetch the newest published version from npm), please confirm this design decision.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between da4c001 and 2a9feff.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (13)
  • apps/create-agentuity/package.json (1 hunks)
  • apps/testing/package.json (1 hunks)
  • package.json (1 hunks)
  • packages/auth/package.json (1 hunks)
  • packages/cli/package.json (1 hunks)
  • packages/core/package.json (1 hunks)
  • packages/react/package.json (1 hunks)
  • packages/runtime/package.json (1 hunks)
  • packages/schema/package.json (1 hunks)
  • packages/server/package.json (1 hunks)
  • packages/test-utils/package.json (1 hunks)
  • packages/vscode/package.json (1 hunks)
  • packages/workbench/package.json (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
packages/*/package.json

📄 CodeRabbit inference engine (AGENTS.md)

Use workspace protocol @agentuity/<package> in package.json dependencies for cross-package imports within the monorepo

Files:

  • packages/workbench/package.json
  • packages/auth/package.json
  • packages/runtime/package.json
  • packages/cli/package.json
  • packages/vscode/package.json
  • packages/test-utils/package.json
  • packages/server/package.json
  • packages/react/package.json
  • packages/core/package.json
  • packages/schema/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/react/**/package.json

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

Peer dependencies must include React 18+ or 19+

Files:

  • packages/react/package.json
🔇 Additional comments (16)
packages/vscode/package.json (1)

5-5: Version bump looks good.

The version increment from 0.0.96 to 0.0.97 aligns with the release objective. No other changes detected.

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

3-3: Version bump looks good.

The version increment aligns with the release. Package correctly maintains "private": true, uses workspace protocol, and has minimal dependencies as per coding guidelines.

packages/react/package.json (1)

3-3: Version bump looks good.

The version increment from 0.0.96 to 0.0.97 aligns with the release objective.

packages/core/package.json (1)

3-3: Version bump looks good.

The version increment from 0.0.96 to 0.0.97 aligns with the release objective. Workspace dependencies use the correct protocol.

package.json (1)

3-3: Version bump looks good.

The root package version increment from 0.0.96 to 0.0.97 aligns with the release objective.

packages/server/package.json (1)

3-3: Version bump looks good.

The version increment from 0.0.96 to 0.0.97 aligns with the release objective. All workspace dependencies use the correct protocol.

packages/cli/package.json (1)

3-3: Version bump looks good.

The version increment from 0.0.96 to 0.0.97 aligns with the release objective. All workspace dependencies use the correct protocol.

packages/auth/package.json (1)

3-3: Version bump looks good.

The version increment from 0.0.96 to 0.0.97 aligns with the release objective. All workspace dependencies use the correct protocol, and React peer dependencies correctly support both 18+ and 19+ as per coding guidelines.

packages/workbench/package.json (2)

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

The version update from 0.0.96 to 0.0.97 aligns with the PR objectives and maintains consistency across the monorepo.


40-41: LGTM! Workspace protocol usage is correct.

All internal @agentuity dependencies correctly use the workspace:* protocol as per the coding guidelines.

Also applies to: 70-70

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

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

The version update from 0.0.96 to 0.0.97 aligns with the PR objectives and maintains consistency across the monorepo.

apps/testing/package.json (1)

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

The version update from 0.0.96 to 0.0.97 aligns with the PR objectives and maintains consistency across the monorepo.

packages/runtime/package.json (2)

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

The version update from 0.0.96 to 0.0.97 aligns with the PR objectives and maintains consistency across the monorepo.


29-31: LGTM! Workspace protocol usage is correct.

All internal @agentuity dependencies correctly use the workspace:* protocol as per the coding guidelines.

Also applies to: 55-55

packages/schema/package.json (2)

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

The version update from 0.0.96 to 0.0.97 aligns with the PR objectives and maintains consistency across the monorepo.


29-29: LGTM! Workspace protocol usage is correct.

All internal @agentuity dependencies correctly use the workspace:* protocol as per the coding guidelines.

Also applies to: 32-32

@jhaynie jhaynie merged commit cf10c49 into main Dec 17, 2025
9 of 10 checks passed
@jhaynie jhaynie deleted the release/0.0.97 branch December 17, 2025 19:34
This was referenced Dec 17, 2025
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