Skip to content

[comp] Production Deploy#2951

Merged
tofikwest merged 5 commits into
releasefrom
main
May 28, 2026
Merged

[comp] Production Deploy#2951
tofikwest merged 5 commits into
releasefrom
main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 28, 2026

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.


Summary by cubic

Deploys the latest release to production. Fixes monorepo workspaces with glob+negation to exclude apps/mcp-server, unblocking npm publish and preserving Docker builds.

  • Bug Fixes

    • Updated root workspaces to ["apps/*", "!apps/mcp-server", "packages/*"] so apps/mcp-server is outside the bun workspace; npm install --ignore-scripts works and API Docker builds no longer fail on missing workspaces.
  • Migration

    • If working on apps/mcp-server, run cd apps/mcp-server && bun install once.

Written for commit ae6cdff. Summary will update on new commits.

Review in cubic

github-actions Bot and others added 3 commits May 28, 2026 19:23
apps/mcp-server is a public npm-published package (@trycompai/mcp-server)
with only npm-public dependencies (@modelcontextprotocol/sdk, express,
zod, @stricli/core). It doesn't import any @trycompai/* workspace
packages, so it doesn't need workspace membership.

WHY THIS IS NECESSARY:
Speakeasy's CI publish flow runs `npm install --ignore-scripts` inside
apps/mcp-server. With apps/mcp-server as a workspace member, npm walks
up to the root package.json, sees the `workspace:*` references in
packages/auth, packages/billing, etc., and fails with EUNSUPPORTEDPROTOCOL
(npm doesn't understand bun's workspace: protocol).

Without the workspace context, npm only reads apps/mcp-server/package.json
(which uses only normal semver versions) and installs cleanly.

LOCAL DEV IMPACT:
Devs working on apps/mcp-server directly will need to run
`cd apps/mcp-server && bun install` once to install its dependencies.
Other apps and packages are unaffected.

In practice apps/mcp-server is regenerated by Speakeasy (`speakeasy run`)
rather than hand-edited, so this is a rare workflow.

Fixes the publish workflow failure in run 26596920929 and the generate
workflow failure in run 26597302360.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…rkspaces

fix(monorepo): exclude apps/mcp-server from bun workspaces
@vercel
Copy link
Copy Markdown

vercel Bot commented May 28, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
app (staging) Ready Ready Preview, Comment May 28, 2026 7:49pm
comp-framework-editor (staging) Ready Ready Preview, Comment May 28, 2026 7:49pm
portal (staging) Ready Ready Preview, Comment May 28, 2026 7:49pm

Request Review

PR #2950 enumerated workspaces explicitly to exclude apps/mcp-server,
but that broke the API's Docker build:

  error: Workspace not found "apps/app"
  error: Workspace not found "apps/framework-editor"
  error: Workspace not found "apps/portal"

The Dockerfile only COPYs apps/api into the build context, so when bun
reads package.json and tries to find the other named apps, it fails.
The original "apps/*" glob worked because globs only match what exists;
explicit paths require the path to exist.

Fix: combine glob with negation —

  ["apps/*", "!apps/mcp-server", "packages/*"]

Verified locally:
- bun install at root succeeds
- node_modules/@trycompai/mcp-server is NOT created
- bun.lock has zero references to apps/mcp-server
- Original Docker-friendly glob behavior preserved (matches only existing paths)

This unbreaks the API Docker build that PR #2950 broke, while still
keeping apps/mcp-server outside the bun workspace so Speakeasy's CI
npm install doesn't choke on workspace:* protocol.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2 files

Confidence score: 5/5

  • Automated review surfaced no issues in the provided summaries.
  • No files require special attention.

Re-trigger cubic

fix(monorepo): unbreak Docker build (workspaces glob+negation)
@tofikwest tofikwest merged commit 264ef1a into release May 28, 2026
9 of 12 checks passed
@claudfuen
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 3.65.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants