mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
Maximiliano Korp
30c6830476
Independently versioned scopes ship on their own cadence, so publishing a scope before the scope that owns one of its workspace: dependencies has shipped emits a dependency range that resolves to nothing. Releasing monorepo before intelligence would put "@copilotkit/intelligence": "^0.1.0" in the published runtime manifest and break every install. Preflight the registry before publishing: for every dependencies entry using the workspace: protocol whose target belongs to a different release scope, require that target's current workspace version to already exist on npm. Reuses the existing npm view error handling, so a network or auth failure still aborts the release instead of being read as "unpublished". The angular and channels scopes pass unchanged (their monorepo dependencies are published at 1.63.2). The monorepo scope is correctly blocked until the intelligence scope ships its first release.