mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Benjamin Taylor
710b5ad783
Adversarial pass on the previous commit. The warning only inspected `workspace:` ranges, so it missed the OTHER way a cross-scope pin goes stale: a literal version range naming a package in another scope. `bumpPackages` rewrites literal ranges for in-scope packages only, so such a pin survives every bump — `scope=all` publishes the canary and the artifact still resolves the dependency's last stable release, silently, which is the exact failure this warning exists to surface. `findCrossScopeWorkspaceDeps` becomes `findCrossScopePins`, reporting both shapes tagged with a `reason`, and the literal case carries its own remedy (convert to `workspace:`) instead of the useless "re-run with scope=all". No such pin exists in the tree today — every cross-scope edge is `workspace:` — so this closes a latent hole rather than a live one, in the one place a future refactor would reintroduce it. Also documents the multi-scope partial-failure mode in prerelease.ts: the cross-scope graph has cycles, so no publish order avoids a package shipping before the same-run version it pins, and npm's no-republish rule means a failed run must be retried under a new suffix.