Skip to content

Release 1.0.1#859

Merged
jhaynie merged 1 commit intomainfrom
release/1.0.1
Feb 3, 2026
Merged

Release 1.0.1#859
jhaynie merged 1 commit intomainfrom
release/1.0.1

Conversation

@jhaynie
Copy link
Member

@jhaynie jhaynie commented Feb 3, 2026

Summary by CodeRabbit

  • Chores
    • Version bump to 1.0.1 across all packages and applications in the monorepo.

@coderabbitai
Copy link

coderabbitai bot commented Feb 3, 2026

📝 Walkthrough

Walkthrough

All package.json files across the monorepo have their version fields updated from 1.0.0 to 1.0.1, including the root package.json and all workspace packages in apps and packages directories.

Changes

Cohort / File(s) Summary
Root Package
package.json
Version field updated from 1.0.0 to 1.0.1.
Application Packages
apps/create-agentuity/package.json, apps/docs/package.json, apps/testing/package.json
Version field updated from 1.0.0 to 1.0.1 in all application packages.
Core & Library Packages
packages/auth/package.json, packages/cli/package.json, packages/core/package.json, packages/drizzle/package.json, packages/evals/package.json, packages/frontend/package.json, packages/opencode/package.json, packages/postgres/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 field updated from 1.0.0 to 1.0.1 across all workspace packages.
🚥 Pre-merge checks | ✅ 1
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ 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 8b86626 and c9b41f9.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (19)
  • apps/create-agentuity/package.json
  • apps/docs/package.json
  • apps/testing/package.json
  • package.json
  • packages/auth/package.json
  • packages/cli/package.json
  • packages/core/package.json
  • packages/drizzle/package.json
  • packages/evals/package.json
  • packages/frontend/package.json
  • packages/opencode/package.json
  • packages/postgres/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 (5)
apps/docs/**/*.json

📄 CodeRabbit inference engine (apps/docs/AGENTS.md)

Workspace dependencies must use workspace:* protocol for local package references (@agentuity/runtime, @agentuity/react, @agentuity/schema, @agentuity/workbench, @agentuity/evals, @agentuity/cli)

Files:

  • apps/docs/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
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
🔇 Additional comments (19)
apps/testing/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 is consistent with the coordinated release across the monorepo.

packages/workbench/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 aligns with the release.

packages/vscode/package.json (1)

5-5: LGTM!

Version bump to 1.0.1 keeps the VSCode extension version synchronized with the SDK release.

packages/core/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 for the core package.

packages/postgres/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 for the postgres package.

apps/docs/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 for the docs app. All local package references correctly use the workspace:* protocol as required. As per coding guidelines, "Workspace dependencies must use workspace:* protocol for local package references."

packages/evals/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 for the evals package.

packages/auth/package.json (1)

3-3: Version bump matches the 1.0.1 release.
Line 3 is a straightforward release version update with no functional impact observed.

packages/runtime/package.json (1)

3-3: Version bump looks correct for 1.0.1.
Line 3 updates the package version as expected.

packages/react/package.json (1)

3-3: Version bump is consistent with the release.
Line 3 updates the package version to 1.0.1.

packages/cli/package.json (1)

3-3: Release version bump is fine.
Line 3 reflects the 1.0.1 update.

package.json (1)

3-3: Root version bump aligns with the release.
Line 3 updates the workspace version to 1.0.1.

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

3-3: Version bump looks good.
Line 3 updates create-agentuity to 1.0.1 as expected.

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

3-3: Test-utils version bump is safe and consistent.
Line 3 updates to 1.0.1 and the package remains private with the minimal dependency footprint.

packages/schema/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 is appropriate. The package correctly maintains only @agentuity/core as a runtime dependency, compliant with guidelines.

packages/server/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 aligns with the release.

packages/opencode/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 aligns with the release.

packages/drizzle/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 aligns with the release.

packages/frontend/package.json (1)

3-3: LGTM!

Version bump to 1.0.1 is appropriate. The package correctly maintains only @agentuity/core as a runtime dependency with no framework-specific dependencies, compliant with guidelines.

✏️ 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.

@github-actions
Copy link

github-actions bot commented Feb 3, 2026

📦 Canary Packages Published

version: 1.0.1-c9b41f9

Packages
Package Version URL
@agentuity/frontend 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-frontend-1.0.1-c9b41f9.tgz
@agentuity/core 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-core-1.0.1-c9b41f9.tgz
@agentuity/drizzle 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-drizzle-1.0.1-c9b41f9.tgz
@agentuity/evals 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-evals-1.0.1-c9b41f9.tgz
@agentuity/runtime 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-runtime-1.0.1-c9b41f9.tgz
@agentuity/auth 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-auth-1.0.1-c9b41f9.tgz
@agentuity/opencode 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-opencode-1.0.1-c9b41f9.tgz
@agentuity/workbench 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-workbench-1.0.1-c9b41f9.tgz
@agentuity/schema 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-schema-1.0.1-c9b41f9.tgz
@agentuity/react 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-react-1.0.1-c9b41f9.tgz
@agentuity/cli 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-cli-1.0.1-c9b41f9.tgz
@agentuity/postgres 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-postgres-1.0.1-c9b41f9.tgz
@agentuity/server 1.0.1-c9b41f9 https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-server-1.0.1-c9b41f9.tgz
Install

Add to your package.json:

{
  "dependencies": {
    "@agentuity/frontend": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-frontend-1.0.1-c9b41f9.tgz",
    "@agentuity/core": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-core-1.0.1-c9b41f9.tgz",
    "@agentuity/drizzle": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-drizzle-1.0.1-c9b41f9.tgz",
    "@agentuity/evals": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-evals-1.0.1-c9b41f9.tgz",
    "@agentuity/runtime": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-runtime-1.0.1-c9b41f9.tgz",
    "@agentuity/auth": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-auth-1.0.1-c9b41f9.tgz",
    "@agentuity/opencode": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-opencode-1.0.1-c9b41f9.tgz",
    "@agentuity/workbench": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-workbench-1.0.1-c9b41f9.tgz",
    "@agentuity/schema": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-schema-1.0.1-c9b41f9.tgz",
    "@agentuity/react": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-react-1.0.1-c9b41f9.tgz",
    "@agentuity/cli": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-cli-1.0.1-c9b41f9.tgz",
    "@agentuity/postgres": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-postgres-1.0.1-c9b41f9.tgz",
    "@agentuity/server": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-server-1.0.1-c9b41f9.tgz"
  }
}

Or install directly:

bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-frontend-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-core-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-drizzle-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-evals-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-runtime-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-auth-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-opencode-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-workbench-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-schema-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-react-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-cli-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-postgres-1.0.1-c9b41f9.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/1.0.1-c9b41f9/agentuity-server-1.0.1-c9b41f9.tgz

@jhaynie jhaynie merged commit f5d07aa into main Feb 3, 2026
15 checks passed
@jhaynie jhaynie deleted the release/1.0.1 branch February 3, 2026 21:54
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