Root Cause Analysis

The nightly release has been failing since 2026-05-19 (3 consecutive days) with TS5055: Cannot write file ... because it would overwrite input file during the tsc --build step in packages/core.

What happens

npm ci in the "Publish Release" job triggers the root prepare script → full build succeeds, creating packages/core/dist/ with .d.ts files.
scripts/version.js bumps workspace versions, then runs npm install --package-lock-only which re-triggers prepare (npm lifecycle behavior).
The second tsc --build for packages/core fails because it attempts to rebuild while dist/ already contains .d.ts output from step 1. TypeScript treats these as both input and output → TS5055.

Why it started on May 19

Commit f97cb680a (PR #4295 — refactor(acp-bridge): create skeleton) merged on May 18 and introduced:

A new packages/acp-bridge workspace with tsconfig.json that has references: [{ "path": "../core" }]
packages/cli/tsconfig.json gained { "path": "../acp-bridge" } in its references
But packages/acp-bridge was not added to the build order in scripts/build.js

This breaks the incremental TypeScript build graph: when tsc --build re-runs for the second time, the unbuilt acp-bridge reference causes TypeScript to re-resolve the core project differently, producing TS5055.

Fix

Add --ignore-scripts to the npm install --package-lock-only in scripts/version.js — the lock-file update doesn't need a full rebuild.
Add packages/acp-bridge to the build order in scripts/build.js before packages/cli.

PR incoming.

Release Failed for v0.15.11-nightly.20260521.ed14a3306 on 2026-05-21 #4368

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions