Genesis managed rollout: deploy --metadata passthrough#1573
Conversation
Rollout intent (source, channel, rollout_org_ids) merges onto the deployment record via --metadata or AGENTUITY_DEPLOY_METADATA; complete may return rolloutId. Supersedes source_blob_id stdout emission approach. Co-authored-by: Cursor <[email protected]>
|
The latest Agentuity deployment details.
View deployment logs with the Agentuity CLI: |
|
Warning Review limit reached
More reviews will be available in 4 minutes and 31 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughAdds deploy rollout metadata support across CLI and server packages. A new ChangesDeploy Rollout Metadata
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
📦 Canary Packages Publishedversion: PackagesInstallAdd to your {
"dependencies": {
"@agentuity/webhook": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-webhook-3.1.1-36a4f15.tgz",
"@agentuity/telemetry": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-telemetry-3.1.1-36a4f15.tgz",
"@agentuity/opencode": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-opencode-3.1.1-36a4f15.tgz",
"@agentuity/hono": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-hono-3.1.1-36a4f15.tgz",
"@agentuity/coder": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-coder-3.1.1-36a4f15.tgz",
"@agentuity/postgres": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-postgres-3.1.1-36a4f15.tgz",
"@agentuity/client": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-client-3.1.1-36a4f15.tgz",
"@agentuity/api": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-api-3.1.1-36a4f15.tgz",
"@agentuity/aigateway": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-aigateway-3.1.1-36a4f15.tgz",
"@agentuity/queue": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-queue-3.1.1-36a4f15.tgz",
"@agentuity/pi": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-pi-3.1.1-36a4f15.tgz",
"@agentuity/email": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-email-3.1.1-36a4f15.tgz",
"@agentuity/sandbox": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-sandbox-3.1.1-36a4f15.tgz",
"@agentuity/claude-code": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-claude-code-3.1.1-36a4f15.tgz",
"@agentuity/vector": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-vector-3.1.1-36a4f15.tgz",
"@agentuity/coder-tui": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-coder-tui-3.1.1-36a4f15.tgz",
"@agentuity/runtime": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-runtime-3.1.1-36a4f15.tgz",
"@agentuity/task": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-task-3.1.1-36a4f15.tgz",
"@agentuity/db": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-db-3.1.1-36a4f15.tgz",
"@agentuity/adapter": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-adapter-3.1.1-36a4f15.tgz",
"@agentuity/analytics": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-analytics-3.1.1-36a4f15.tgz",
"@agentuity/server": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-server-3.1.1-36a4f15.tgz",
"@agentuity/drizzle": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-drizzle-3.1.1-36a4f15.tgz",
"@agentuity/keyvalue": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-keyvalue-3.1.1-36a4f15.tgz",
"@agentuity/config": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-config-3.1.1-36a4f15.tgz",
"create-agentuity": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/create-agentuity-3.1.1-36a4f15.tgz",
"@agentuity/migrate": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-migrate-3.1.1-36a4f15.tgz",
"@agentuity/schedule": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-schedule-3.1.1-36a4f15.tgz",
"@agentuity/cli": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-cli-3.1.1-36a4f15.tgz",
"@agentuity/schema": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-schema-3.1.1-36a4f15.tgz",
"@agentuity/core": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-core-3.1.1-36a4f15.tgz",
"@agentuity/vite": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-vite-3.1.1-36a4f15.tgz",
"@agentuity/storage": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-storage-3.1.1-36a4f15.tgz",
"@agentuity/stream": "https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-stream-3.1.1-36a4f15.tgz"
}
}Or install directly: bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-webhook-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-telemetry-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-opencode-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-hono-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-coder-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-postgres-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-client-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-api-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-aigateway-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-queue-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-pi-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-email-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-sandbox-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-claude-code-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-vector-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-coder-tui-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-runtime-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-task-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-db-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-adapter-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-analytics-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-server-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-drizzle-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-keyvalue-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-config-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/create-agentuity-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-migrate-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-schedule-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-cli-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-schema-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-core-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-vite-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-storage-3.1.1-36a4f15.tgz
bun add https://agentuity-sdk-objects.t3.storageapi.dev/npm/3.1.1-36a4f15/agentuity-stream-3.1.1-36a4f15.tgz |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
packages/cli/src/cmd/cloud/deploy/build.ts (1)
188-188: 🧹 Nitpick | 🔵 Trivial | ⚡ Quick winRemove duplicate metadata merge.
This merge at line 188 is redundant because line 206 performs the same merge for both the agentuity and non-agentuity branches. The call at line 188 parses the metadata JSON and merges it, then line 206 immediately repeats both operations, overwriting the result.
♻️ Proposed fix
if (registeredProjectName) { build.project.name = registeredProjectName; } - build = mergeDeployRolloutMetadata(build, resolveDeployRolloutMetadata(deployOptions)); } else {🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@packages/cli/src/cmd/cloud/deploy/build.ts` at line 188, The call to mergeDeployRolloutMetadata with resolveDeployRolloutMetadata at line 188 is redundant and should be removed because the same merge operation is performed again at line 206, which immediately overwrites the result from line 188. Simply delete the entire line 188 containing the redundant mergeDeployRolloutMetadata call to eliminate the duplicate metadata merge operation.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@packages/cli/src/deploy-rollout-metadata.ts`:
- Around line 1-64: Run the formatting command `bun run format` to automatically
fix all formatting issues in the deploy-rollout-metadata.ts file according to
the project's Biome configuration settings (tabs width 3, single quotes,
semicolons, lineWidth 100, and trailingCommas es5).
---
Nitpick comments:
In `@packages/cli/src/cmd/cloud/deploy/build.ts`:
- Line 188: The call to mergeDeployRolloutMetadata with
resolveDeployRolloutMetadata at line 188 is redundant and should be removed
because the same merge operation is performed again at line 206, which
immediately overwrites the result from line 188. Simply delete the entire line
188 containing the redundant mergeDeployRolloutMetadata call to eliminate the
duplicate metadata merge operation.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 94d2e44e-ff2b-4b4d-80d7-c3ab6e243192
📒 Files selected for processing (6)
packages/cli/src/cmd/cloud/deploy.tspackages/cli/src/cmd/cloud/deploy/build.tspackages/cli/src/deploy-rollout-metadata.tspackages/cli/src/types.tspackages/core/src/env.d.tspackages/server/src/api/project/deploy.ts
📜 Review details
⏰ Context from checks skipped due to timeout. (17)
- GitHub Check: Native install (Linux)
- GitHub Check: Linux distro install smoke
- GitHub Check: Bun version checks
- GitHub Check: Native install (macOS)
- GitHub Check: Installer scenarios
- GitHub Check: Queue CLI Tests (node)
- GitHub Check: Package Installation & Usage Test (node)
- GitHub Check: Service Client Smoke Tests
- GitHub Check: Queue CLI Tests (bun)
- GitHub Check: Framework Demo Tests
- GitHub Check: Postgres SSL Integration Test
- GitHub Check: Migrate Chain (v1 → v2 → v3)
- GitHub Check: Package Installation & Usage Test (bun)
- GitHub Check: Windows WSL CLI Smoke Test
- GitHub Check: Pack & Upload
- GitHub Check: Build
- GitHub Check: Agentuity - docs-docs
🧰 Additional context used
📓 Path-based instructions (6)
**/*.{ts,tsx,js,jsx}
📄 CodeRabbit inference engine (AGENTS.md)
Run
bun run formatusing Biome with tabs (width 3), single quotes, semicolons, lineWidth 100, and trailingCommas es5
Files:
packages/cli/src/types.tspackages/core/src/env.d.tspackages/cli/src/deploy-rollout-metadata.tspackages/cli/src/cmd/cloud/deploy/build.tspackages/server/src/api/project/deploy.tspackages/cli/src/cmd/cloud/deploy.ts
**/*.{ts,tsx}
📄 CodeRabbit inference engine (AGENTS.md)
**/*.{ts,tsx}: Use TypeScript in strict mode with ESNext target and bundler moduleResolution
UseStructuredErrorfrom@agentuity/corefor error handling
Files:
packages/cli/src/types.tspackages/core/src/env.d.tspackages/cli/src/deploy-rollout-metadata.tspackages/cli/src/cmd/cloud/deploy/build.tspackages/server/src/api/project/deploy.tspackages/cli/src/cmd/cloud/deploy.ts
packages/cli/src/**/*.ts
📄 CodeRabbit inference engine (packages/cli/AGENTS.md)
packages/cli/src/**/*.ts: Usetui.*helpers for formatted output (header,info,success,warning,error,table,progress)
Usectx.loggerfor logging;logger.fatal()logs and exits with code 1
Useawait readFile(p, 'utf-8')andawait writeFile(p, content)fromnode:fs/promisesfor file I/O
ImportpathExistsfromnode-compat/fsfor file existence checks instead of using Node's built-in
Do not use Bun globals (Bun.file,Bun.spawn,Bun.color,Bun.stringWidth, etc.) in production source code;tsconfig.jsontype checking enforces this
Imports must use explicit.tsextensions for relative paths (e.g.,from './foo.ts', notfrom './foo'); TypeScript'srewriteRelativeImportExtensionswill rewrite them to.jsin output
Always checkisJSONMode()for machine-readable output in command handlers
UserequireAuth(ctx)oroptionalAuth(ctx)for authenticated commands
Files:
packages/cli/src/types.tspackages/cli/src/deploy-rollout-metadata.tspackages/cli/src/cmd/cloud/deploy/build.tspackages/cli/src/cmd/cloud/deploy.ts
packages/core/src/**/*.ts
📄 CodeRabbit inference engine (packages/core/AGENTS.md)
packages/core/src/**/*.ts: Build TypeScript code usingbun run buildwhich compiles with tsc
Run TypeScript type checking withbun run typecheck
Ensure runtime compatibility with both Browser and Node/Bun environments - no runtime-specific code
Use ESNext as build target with TypeScript declaration files
Use TypeScript-first development - all code must be TypeScript
Prefer interfaces for public APIs
Use generics for reusable type utilities
Ensure no framework coupling - code must work in any JavaScript environment
Many exports aretypeorinterfaceonly - usetypekeyword for type-only exports
Ensure all exports are pure with no side effects or global mutations
All relative imports in TypeScript files MUST include the.tsextension for proper ESM module resolution
Files:
packages/core/src/env.d.ts
packages/server/src/**/*.{ts,tsx}
📄 CodeRabbit inference engine (packages/server/AGENTS.md)
All code must be TypeScript
Files:
packages/server/src/api/project/deploy.ts
packages/server/src/**/*.ts
📄 CodeRabbit inference engine (packages/server/AGENTS.md)
packages/server/src/**/*.ts: Use zod for runtime validation
Always use.tsextensions in relative imports (e.g.,from '../api.ts', notfrom '../api'). This is required for Node.js ESM compatibility —tscrewrites.ts→.jsin compiled output, but leaves extensionless imports untouched, which breaks Node.js module resolution. This is enforced by theuseImportExtensionsBiome lint rule.
Files:
packages/server/src/api/project/deploy.ts
🧠 Learnings (5)
📚 Learning: 2025-12-21T00:31:41.858Z
Learnt from: jhaynie
Repo: agentuity/sdk PR: 274
File: packages/cli/src/cmd/build/vite/server-bundler.ts:12-41
Timestamp: 2025-12-21T00:31:41.858Z
Learning: In Bun runtime, BuildMessage and ResolveMessage are global types and are not exported from the bun module. Do not import { BuildMessage } from 'bun' or similar; these types are available globally and should be used without import. This applies to all TypeScript files that target the Bun runtime within the repository.
Applied to files:
packages/cli/src/types.tspackages/core/src/env.d.tspackages/cli/src/deploy-rollout-metadata.tspackages/cli/src/cmd/cloud/deploy/build.tspackages/server/src/api/project/deploy.tspackages/cli/src/cmd/cloud/deploy.ts
📚 Learning: 2026-02-17T14:23:15.448Z
Learnt from: potofpie
Repo: agentuity/sdk PR: 974
File: packages/cli/src/cmd/git/account/list.ts:39-40
Timestamp: 2026-02-17T14:23:15.448Z
Learning: In the Agentuity CLI framework (packages/cli), when a subcommand declares requires: { auth: true }, the framework will automatically call requireAuth() before invoking the handler. Do not call requireAuth(ctx) manually inside command handlers. This applies to all TypeScript command files under packages/cli/src, including paths like packages/cli/src/cmd/git/account/list.ts.
Applied to files:
packages/cli/src/types.tspackages/cli/src/deploy-rollout-metadata.tspackages/cli/src/cmd/cloud/deploy/build.tspackages/cli/src/cmd/cloud/deploy.ts
📚 Learning: 2026-01-13T04:32:02.691Z
Learnt from: jhaynie
Repo: agentuity/sdk PR: 565
File: packages/cli/src/cmd/cloud/region-lookup.ts:14-26
Timestamp: 2026-01-13T04:32:02.691Z
Learning: Enforce sandbox identifier prefixes in new code within the CLI cloud region lookup: new sandboxes must use the sbx_ prefix. The snbx_ prefix may appear in legacy code or examples, but do not use snbx_ for new sandboxes. When reviewing changes in packages/cli/src/cmd/cloud/, ensure any created sandbox identifiers use sbx_ and remove or migrate any snbx_ usages in newly added code.
Applied to files:
packages/cli/src/cmd/cloud/deploy/build.tspackages/cli/src/cmd/cloud/deploy.ts
📚 Learning: 2025-12-19T14:19:33.765Z
Learnt from: jhaynie
Repo: agentuity/sdk PR: 259
File: packages/cli/src/cmd/build/vite/registry-generator.ts:306-312
Timestamp: 2025-12-19T14:19:33.765Z
Learning: Route files under src/api should use the .ts extension only (no .tsx) and regex patterns for such paths should anchor to \.ts$ (e.g., /\/.ts$/). Agent files may support both .ts and .tsx, but route files in the Agentuity SDK codebase are restricted to .ts. This guideline applies to all similar route files under src/api across the repository.
Applied to files:
packages/server/src/api/project/deploy.ts
📚 Learning: 2025-12-30T00:13:37.849Z
Learnt from: jhaynie
Repo: agentuity/sdk PR: 355
File: packages/server/src/api/sandbox/util.ts:2-6
Timestamp: 2025-12-30T00:13:37.849Z
Learning: In the packages/server tree, treat code as runtime-agnostic between Node.js and Bun. Ensure TypeScript files (e.g., util.ts) import and use APIs in a way that works under both runtimes. It is acceptable to rely on Bun’s Node.js compatibility for built-ins accessed via the node: namespace (e.g., node:events, node:stream, node:buffer). During reviews, prefer patterns and imports that remain compatible with Bun's environment, and flag any hard dependencies on runtime-specific globals or non-portable Node APIs.
Applied to files:
packages/server/src/api/project/deploy.ts
🪛 GitHub Actions: Biome / 0_Format & Lint.txt
packages/cli/src/cmd/cloud/deploy.ts
[error] 1-1: Biome format check failed: File content differs from formatting output.
🪛 GitHub Actions: Biome / Format & Lint
packages/cli/src/cmd/cloud/deploy.ts
[error] 1-1: Biome formatting check failed: File content differs from formatting output.
🪛 GitHub Check: Format & Lint
packages/cli/src/deploy-rollout-metadata.ts
[failure] 1-1: format
File content differs from formatting output
🔇 Additional comments (7)
packages/cli/src/types.ts (1)
622-627: LGTM!packages/core/src/env.d.ts (1)
175-177: LGTM!packages/server/src/api/project/deploy.ts (1)
215-217: LGTM!Also applies to: 313-316
packages/cli/src/cmd/cloud/deploy/build.ts (1)
206-206: LGTM!packages/cli/src/cmd/cloud/deploy.ts (3)
170-170: LGTM!
401-401: LGTM!
835-835: LGTM!
Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
1 participant
Summary
--metadata/AGENTUITY_DEPLOY_METADATAonagentuity deploymerges Genesis rollout intent onto the deployment recordsource: managed,channel(edge|stable|commit), optionalrollout_org_idsrolloutIdfrom deploy complete when app fan-out runsReplaces closed #1572 (source_blob_id stdout emission).
Merge order
Before agentuity/infra#737 and agentuity/app#1349
Test plan
--metadata '{"source":"managed","channel":"edge"}'merges fields into build metadata