Files
Benjamin Taylor bee19e78df fix(release): make canary publishes reachable and cross-scope composable
Two release-tooling defects turned a pair of canary publishes into a broken
combination for consumers (a canary runtime resolving the last STABLE
channels-intelligence, which still called the removed `channel.addAdapter`).

1. Canary versions were prereleases of an ALREADY-PUBLISHED version. A stable
   release leaves the working tree on the version it just published, and
   computePrereleaseVersion appended `-canary.<id>` to exactly that, so the
   canary sorted BELOW its own release (`0.2.1-canary.x < 0.2.1`): the `canary`
   dist-tag pointed behind `latest`, and no dependent range could ever resolve
   it. Base the canary on the next unreleased version instead (patch bump,
   reusing computeNextStableVersion's prerelease rule).

2. A canary published one scope at a time, but the scopes are only independent
   on the version axis. `@copilotkit/runtime` carries
   `"@copilotkit/channels-intelligence": "workspace:*"`, and `pnpm pack`
   resolves that against the working tree — so a `monorepo` canary pinned the
   channels family to its last stable release even when the commit changed both
   sides of the contract. Add a prerelease-only `all` selector that bumps and
   publishes every scope from one commit under one shared canary id, and warn
   loudly when a single-scope canary leaves a cross-scope pin behind.

`all` is a selector, never a scope: stable releases stay single-scope (their
tag, release branch, and npm/Slack links all derive from one scope name), which
publish-release.yml enforces in both jobs and the dropdown guard enforces per
workflow.
2026-07-24 15:53:13 -05:00

68 lines
2.2 KiB
TypeScript

import fs from "fs";
import path from "path";
import { fileURLToPath } from "url";
export const ROOT = path.resolve(
path.dirname(fileURLToPath(import.meta.url)),
"../../..",
);
export type ReleaseScope = "monorepo" | "angular" | "channels";
export interface ScopeConfig {
packages: string[];
versionSource: string;
sharedVersion: boolean;
}
export interface ReleaseConfig {
prereleaseTag: string;
scopes: Record<ReleaseScope, ScopeConfig>;
}
export function loadConfig(): ReleaseConfig {
const configPath = path.join(ROOT, "release.config.json");
return JSON.parse(fs.readFileSync(configPath, "utf8"));
}
/**
* Sentinel `scope` value selecting EVERY scope in release.config.json.
*
* Canary-only (the stable lane derives its tag and release branch from a single
* scope name). It exists because scopes are only independent on the version
* axis, not the dependency axis: `@copilotkit/runtime` carries
* `"@copilotkit/channels-intelligence": "workspace:*"`, and `pnpm pack`
* rewrites that against whatever is in the working tree. A canary of one scope
* therefore ships pinned to the OTHER scope's last stable release, which is a
* broken combination whenever the change spans both. Publishing every scope
* from one commit rewrites those pins to same-run canary versions instead.
*/
export const ALL_SCOPES = "all";
/**
* Resolve a dispatched `scope` input into the concrete scopes to act on:
* {@link ALL_SCOPES} expands to every scope in release.config.json order, any
* other value must name exactly one scope.
*/
export function resolveScopes(selector: string): ReleaseScope[] {
const scopes = Object.keys(loadConfig().scopes) as ReleaseScope[];
if (selector === ALL_SCOPES) return scopes;
if (!scopes.includes(selector as ReleaseScope)) {
throw new Error(
`Unknown scope: ${selector}. Valid scopes: ${[...scopes, ALL_SCOPES].join(", ")}`,
);
}
return [selector as ReleaseScope];
}
export function getScopeConfig(scope: ReleaseScope): ScopeConfig {
const config = loadConfig();
const scopeConfig = config.scopes[scope];
if (!scopeConfig) {
throw new Error(
`Unknown scope: ${scope}. Valid scopes: ${Object.keys(config.scopes).join(", ")}`,
);
}
return scopeConfig;
}