-
Notifications
You must be signed in to change notification settings - Fork 82
make pnpm dev run build in workspaces I depend on first, rename turbo.json to turbo.jsonc
#1146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| "check:fix": "biome check --write", | ||
| "clean": "pnpm -r --parallel exec rm -rf node_modules dist build .next .turbo", | ||
| "clean:turbo": "rm -rf .turbo", | ||
| "clean": "pnpm -r --parallel exec rm -rf node_modules/ dist/ build/ .next/ .turbo/ esm/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added esm directory from @inkeep/agents-manage-mcp
|
Claude finished @dimaMachina's task —— View job PR Review: Build Dependencies and Turbo ConfigurationI've completed a comprehensive review of this PR that addresses build dependency issues and Turbo configuration updates. Here's my detailed analysis: 🎯 Core Fix Analysis✅ Primary Issue Resolution 🔧 Technical Changes Review1. Turbo Configuration (turbo.json → turbo.jsonc)
2. Package Configuration Updates
3. Dockerfile Updates
📋 Code Quality AssessmentAPI Changes (agents-manage-api/src/middleware/require-permission.ts)
UI Changes (agents-manage-ui/)
SDK & Core Updates
🏗️ Architectural ConsiderationsBuild Pipeline Impact
Workspace Dependencies
🚨 Potential Issues & RecommendationsCritical
Medium Priority
Low Priority
🧪 Testing & ValidationWhat's Covered
Missing Verification
🎯 Customer ImpactPositive
Risk Assessment
📝 Final RecommendationsBefore Merge
Overall AssessmentThis PR addresses the core issue effectively with a clean, maintainable solution. The architectural approach is sound, and the code quality is high. The primary concern is the deployment failure that needs immediate attention. The change is architecturally sound and follows best practices for monorepo build orchestration. Once the deployment issue is resolved, this should be safe to merge. |
…tor retrieving `relationshipId` in agents-core (#1153) * refactor Agent * add createRelationToolName and getRelationshipIdForTool * upd * upd * fix * fix circle * Fix blue dot issue and refactor relationshipId retrieval Fixes an issue with the blue dot appearing on inverted delegation and refactors the retrieval of relationshipId in agents-core. * Apply suggestions from code review
|
This pull request has been automatically marked as stale because it has not had recent activity. If this PR is still relevant:
Thank you for your contributions! |
I've run into issue where
pnpm devfails due missingbuildcommand in@inkeep/agents-manage-mcp