Release 0.1.0 (Beta)

[jhaynie]

Summary by CodeRabbit

• Chores
  • Bumped all package versions to 0.1.0 across the monorepo. No functional changes or behavioral updates included in this release.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Version field updated from 0.0.112 to 0.1.0 across 15 package.json files in the monorepo, including the root package.json, apps directory, and packages directory. No functional or behavioral changes.

Changes

Cohort / File(s)	Summary
Root package.json	Version bumped: 0.0.112 → 0.1.0
Apps apps/create-agentuity/package.json, apps/testing/package.json	Version bumped: 0.0.112 → 0.1.0
Packages 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	Version bumped: 0.0.112 → 0.1.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Release 0.0.112 #433: Previous version bump across the same package.json files (0.0.111 → 0.0.112)
• Release 0.0.102 #310: Similar monorepo-wide version bump pattern across package.json files
• Release 0.0.108 #381: Related version increment updates to multiple package.json files in the monorepo

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.1.0

---

📜 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 d827236 and 4d00fff.

⛔ 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)

packages/schema/**/package.json

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

Only depends on @agentuity/core for StandardSchema types

Files:

• packages/schema/package.json

packages/frontend/**/package.json

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

Do not add framework-specific dependencies to package.json - maintain workspace dependency on @agentuity/core only

Files:

• packages/frontend/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/test-utils/**

📄 CodeRabbit inference engine (AGENTS.md)

The @agentuity/test-utils package is private and should never be published

Files:

• packages/test-utils/package.json

🔇 Additional comments (15)

packages/workbench/package.json (1)

3-3: LGTM! Version bump is correct.

The version update to 0.1.0 aligns with the release objectives and is consistent across the monorepo.

packages/runtime/package.json (1)

3-3: LGTM! Version bump is correct.

The version update to 0.1.0 is consistent with the beta release.

package.json (1)

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

The root package version update to 0.1.0 is appropriate for this beta release.

packages/evals/package.json (1)

3-3: LGTM! Version bump is correct.

The version update to 0.1.0 aligns with the beta release across the monorepo.

packages/cli/package.json (1)

3-3: LGTM! Version bump is correct.

The version update to 0.1.0 is consistent with the beta release strategy.

packages/schema/package.json (1)

3-3: LGTM! Version bump is correct.

The version has been properly updated to 0.1.0 for the beta release, and the dependencies remain compliant with the coding guidelines (only depends on @agentuity/core).

packages/core/package.json (1)

3-3: LGTM! Version bump is correct.

The version has been properly updated to 0.1.0 for the beta release. No dependency changes were made.

packages/frontend/package.json (1)

3-3: LGTM! Version bump is correct.

The version has been properly updated to 0.1.0 for the beta release, and the dependencies remain compliant with the coding guidelines (maintains workspace dependency on @agentuity/core only, no framework-specific dependencies).

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

3-3: LGTM! Version bump is correct.

The version has been properly updated to 0.1.0 for the beta release. The dependency on @agentuity/cli using "latest" is appropriate for this CLI wrapper package.

packages/vscode/package.json (1)

5-5: Version bump to 0.1.0 is correct and consistently applied.

Verification confirms that all 15 package.json files mentioned in the AI summary have been properly updated to version 0.1.0: root, 2 core apps (create-agentuity, testing), and all 12 packages (auth, cli, core, evals, frontend, react, runtime, schema, server, test-utils, vscode, workbench). Testing sub-apps, examples, and templates correctly remain at 0.0.1.

apps/testing/package.json (1)

3-3: LGTM!

Version bump to 0.1.0 is consistent with the release. Package is correctly marked as private.

packages/auth/package.json (1)

3-3: LGTM!

Version bump to 0.1.0 aligns with the release. Dependencies and workspace references are properly configured.

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

3-5: LGTM!

Version bump to 0.1.0 is correct. As per coding guidelines, the package properly has "private": true set and uses only @agentuity/core and bun-types as dependencies to minimize dependency footprint.

packages/react/package.json (1)

3-3: LGTM!

Version bump to 0.1.0 aligns with the release. Package configuration for public publishing is correct.

packages/server/package.json (1)

3-3: LGTM!

Version bump to 0.1.0 aligns with the release. Package configuration and dependencies are properly set up.

---

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