fix: remove agent from pnpm workspace to fix Render build#54
Merged
GeneralJerel merged 3 commits intomainfrom Mar 25, 2026
Merged
fix: remove agent from pnpm workspace to fix Render build#54GeneralJerel merged 3 commits intomainfrom
GeneralJerel merged 3 commits intomainfrom
Conversation
The postinstall "uv sync" hook runs during pnpm install on the frontend Node service where uv is not available. The agent service has its own buildCommand in render.yaml. Also updates dev script to match the new native FastAPI setup and drops the unused langgraph-cli dependency.
The agent's package.json made it a pnpm workspace member, so pnpm install on the Node frontend service triggered "uv sync" in an environment where uv doesn't exist — breaking Render deploys. Remove apps/agent/package.json entirely (matching the Shadify pattern) and run the agent dev server via a direct shell command in the root package.json instead of through Turbo.
The agent is no longer a pnpm workspace member, so setup-python and setup-uv are unnecessary in CI. Their post-job cache step failed because uv never ran. Also drop Python from the smoke matrix (8→4 jobs) and add `wait` after killing the frontend process to suppress the SIGTERM exit code that was failing the smoke step.
GeneralJerel
force-pushed
the
fix/native-python-agent
branch
from
62fcea9 to
70f9184
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apps/agent/package.jsonso the Python agent is no longer a pnpm workspace memberpackage.jsonto run agent dev server via direct shell command instead of Turbopnpm-workspace.yamlProblem
PR #53 switched the agent from Docker to native FastAPI but left
apps/agent/package.jsonwith apostinstall: "uv sync"hook. When Render's frontend Node service runspnpm install, it installs all workspace members — triggeringuv syncin an environment whereuvdoesn't exist, crashing the build.Solution
Match the Shadify pattern: keep the Python agent in
apps/agent/but outside the pnpm workspace entirely. Without apackage.json, pnpm ignores it. The agent's Render service already has its ownbuildCommandinrender.yaml.Test plan
pnpm installsucceeds without triggering anyuvcommandspnpm lsshows no@repo/agentworkspace memberpnpm dev:agentstarts uvicorn on port 8123🤖 Generated with Claude Code