skills/copilotkit__copilotkit
1
0
Fork 0
mirror of https://github.com/CopilotKit/CopilotKit.git synced 2026-09-14 16:26:20 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
copilotkit__copilotkit/release.config.json
T

49 lines
1.4 KiB
JSON
Raw Permalink Normal View History

ci: add bespoke stateless release system Replace changesets with a simple, stateless release system: Stable release (PR-gated): Actions → "create release PR" → pick patch/minor/major → CI runs → merge → publishes to npm, creates git tag + GitHub Release Prerelease (ad-hoc): Actions → "publish / prerelease" → publishes current version with -canary.<suffix|timestamp> to npm under "canary" tag Key features: - All 12 core @copilotkit/* packages share a single version - AI-generated release notes via Anthropic API - Notion draft for team editing before merge - Notion link commented on the release PR - Guards: concurrent release PR check, version > npm check, clean semver check, canary-only prerelease tag - release/publish/v* branch pattern (hard to accidentally match) - TypeScript throughout (tsx runner) - release.config.json with versionedTogether/versionedIndependently
2026-04-10 22:18:11 -07:00
{
"prereleaseTag": "canary",
ci: add scope dropdown (monorepo, cli, angular) to release workflows Each release scope has its own packages, version source, and independent version track: - monorepo: 12 core @copilotkit/* packages (shared version) - cli: copilotkit CLI (independent version) - angular: @copilotkitnext/angular (independent version) Branch pattern is now release/publish/<scope>/v<version> and git tags use <scope>/v<version> for non-monorepo scopes.
2026-04-10 23:04:48 -07:00
"scopes": {
"monorepo": {
"packages": [
"@copilotkit/a2ui-renderer",
chore(release): include @copilotkit/agentcore-runner in monorepo scope The package was added to the repo but never wired into release.config.json, so the release / create-pr and release / publish workflows skipped it. Adding it here lets the next monorepo release bump and publish it like its siblings (e.g. @copilotkit/sqlite-runner). sharedVersion=true means the existing 1.56.2 in package.json will be overwritten with the monorepo's next version.
2026-05-07 15:15:50 +00:00
"@copilotkit/agentcore-runner",
ci: add scope dropdown (monorepo, cli, angular) to release workflows Each release scope has its own packages, version source, and independent version track: - monorepo: 12 core @copilotkit/* packages (shared version) - cli: copilotkit CLI (independent version) - angular: @copilotkitnext/angular (independent version) Branch pattern is now release/publish/<scope>/v<version> and git tags use <scope>/v<version> for non-monorepo scopes.
2026-04-10 23:04:48 -07:00
"@copilotkit/core",
feat(react-core): consume shared mcp-apps-renderer, drop direct MCP deps Reduce MCPAppsActivityRenderer from a 786-line self-contained implementation to a thin React adapter over the framework-agnostic bindMcpApp: - the React shell owns the iframe (create / mount / size / remove) and wires the session hooks (onResource, onSizeChanged, onError) to React state; all protocol logic (AppBridge, sandbox proxy, request queue, ui/message + open-link, tool input/result) now lives in @copilotkit/mcp-apps-renderer - the bridge-free activity surface (MCPAppsActivityType, content schema, follow-up runner) is re-exported statically from the package's new ./activity entry, so registering the activity does not pull the ext-apps bundle - bindMcpApp is loaded via a lazy import("@copilotkit/mcp-apps-renderer") inside the effect, keeping ext-apps (~40-50 kB gzipped) out of the main chunk Dependency move (FR-007): react-core drops its direct @modelcontextprotocol/ext-apps dependency, the @modelcontextprotocol/sdk peer + devDependency, and the zod >=3.25 peer floor (reverted to >=3.0.0), and depends on @copilotkit/mcp-apps-renderer instead. The package becomes the sole owner of the MCP libraries: sdk moves from a peer to a dependency there (satisfying ext-apps' required sdk peer), and a bridge-free ./activity subpath is exported. Register the package in the monorepo release scope and regenerate the public API manifest. react-core's MCP e2e suite (37 tests across 4 files) stays green; check-types + oxlint clean; behavior-preserving.
2026-09-04 05:59:13 +01:00
"@copilotkit/mcp-apps-renderer",
ci: add scope dropdown (monorepo, cli, angular) to release workflows Each release scope has its own packages, version source, and independent version track: - monorepo: 12 core @copilotkit/* packages (shared version) - cli: copilotkit CLI (independent version) - angular: @copilotkitnext/angular (independent version) Branch pattern is now release/publish/<scope>/v<version> and git tags use <scope>/v<version> for non-monorepo scopes.
2026-04-10 23:04:48 -07:00
"@copilotkit/react-core",
chore: wire @copilotkit/react-native into release system Add to monorepo scope in release.config.json. Set version to 1.56.5, correct ESM extensions in exports map, add check-types/publint/attw scripts, align tsdown to ^0.20.3. Add react-native example glob to pnpm-workspace.yaml. Regenerate lockfile preserving zod@3 and langchain dependency versions.
2026-05-06 16:42:43 -07:00
"@copilotkit/react-native",
ci: add scope dropdown (monorepo, cli, angular) to release workflows Each release scope has its own packages, version source, and independent version track: - monorepo: 12 core @copilotkit/* packages (shared version) - cli: copilotkit CLI (independent version) - angular: @copilotkitnext/angular (independent version) Branch pattern is now release/publish/<scope>/v<version> and git tags use <scope>/v<version> for non-monorepo scopes.
2026-04-10 23:04:48 -07:00
"@copilotkit/react-textarea",
"@copilotkit/react-ui",
"@copilotkit/runtime",
"@copilotkit/runtime-client-gql",
"@copilotkit/sdk-js",
"@copilotkit/shared",
"@copilotkit/sqlite-runner",
"@copilotkit/voice",
feat(vue): add v1 wrappers, A2UI Vue-native renderer, and CR parity fixes V1 CopilotKit.vue provider wrapper with backward-compatible API, A2UI adapter/surface/catalog context/built-in tool-call renderer for Vue-native rendering, capability and custom message hooks, config allowlist and release config updates.
2026-05-13 15:13:56 -07:00
"@copilotkit/vue",
fix(release): fold web-components into monorepo scope
2026-07-01 09:54:51 -07:00
"@copilotkit/web-components",
ci: add scope dropdown (monorepo, cli, angular) to release workflows Each release scope has its own packages, version source, and independent version track: - monorepo: 12 core @copilotkit/* packages (shared version) - cli: copilotkit CLI (independent version) - angular: @copilotkitnext/angular (independent version) Branch pattern is now release/publish/<scope>/v<version> and git tags use <scope>/v<version> for non-monorepo scopes.
2026-04-10 23:04:48 -07:00
"@copilotkit/web-inspector"
],
"versionSource": "@copilotkit/react-core",
"sharedVersion": true
},
"angular": {
chore: prepare angular package release
2026-06-18 13:49:35 -07:00
"packages": ["@copilotkit/angular"],
"versionSource": "@copilotkit/angular",
ci: add scope dropdown (monorepo, cli, angular) to release workflows Each release scope has its own packages, version source, and independent version track: - monorepo: 12 core @copilotkit/* packages (shared version) - cli: copilotkit CLI (independent version) - angular: @copilotkitnext/angular (independent version) Branch pattern is now release/publish/<scope>/v<version> and git tags use <scope>/v<version> for non-monorepo scopes.
2026-04-10 23:04:48 -07:00
"sharedVersion": false
feat(release): npm release scopes for bot(+bot-ui) and bot-slack - release.config.json: 'bot' scope versions @copilotkit/bot and @copilotkit/bot-ui together (sharedVersion: true, source: bot); 'bot-slack' is its own scope, mirroring the angular precedent - ReleaseScope type + VALID_SCOPES arrays + usage strings extended across release scripts - stable-release.yml / publish-release.yml: scope choice options - bot, bot-ui, bot-slack manifests: drop private, add publishConfig (public), repository/homepage/keywords, publint/attw targets; first release v0.0.1 - internal bot-package deps use workspace:~ (tilde): caret on a 0.0.x version pins the exact patch, tilde tracks the 0.0.x line; core/shared stay workspace:^ (caret is correct at 1.x) Verified: release-script tests 85/85; prepare-release --scope bot --dry-run bumps bot AND bot-ui in lockstep; actionlint clean on touched lines. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-10 10:14:06 -07:00
},
refactor(channels): rename @copilotkit/bot* packages to @copilotkit/channels* (OSS-438) Renames the Bots SDK to the Channels SDK. Names only — no behavior change. - 8 packages @copilotkit/bot* -> @copilotkit/channels* (git mv dirs, names, workspace: cross-deps). Now includes @copilotkit/bot-intelligence -> @copilotkit/channels-intelligence (landed on main via #5761; unpublished, so renamed fresh with the family). - release.config.json scope keys + versionSource; ReleaseScope union; canary/stable-release/publish-release scope dropdowns; verify script - examples/slack (Kite) + examples/teams: deps, jsxImportSource, imports - showcase/shell-docs: content dirs docs/bots->docs/channels and reference/bot->reference/channels, nav registry, redirects createBot and other API names unchanged. Old @copilotkit/bot* to be deprecated after the new packages publish (bot-intelligence was never published). Re-derived onto latest main (was conflicting after #5761 landed). Refs OSS-438
2026-07-08 13:07:02 -05:00
"channels": {
chore(release): unify channels version scope
2026-07-14 22:45:42 -07:00
"packages": [
"@copilotkit/channels-ui",
fix(release): stage channels publishing
2026-07-14 23:05:50 -07:00
"@copilotkit/channels-core",
chore(release): unify channels version scope
2026-07-14 22:45:42 -07:00
"@copilotkit/channels-slack",
"@copilotkit/channels-teams",
fix(release): stage channels publishing
2026-07-14 23:05:50 -07:00
"@copilotkit/channels-intelligence",
"@copilotkit/channels-discord",
chore(release): unify channels version scope
2026-07-14 22:45:42 -07:00
"@copilotkit/channels-telegram",
fix(release): stage channels publishing
2026-07-14 23:05:50 -07:00
"@copilotkit/channels-whatsapp",
"@copilotkit/channels"
chore(release): unify channels version scope
2026-07-14 22:45:42 -07:00
],
refactor(channels): rename @copilotkit/bot* packages to @copilotkit/channels* (OSS-438) Renames the Bots SDK to the Channels SDK. Names only — no behavior change. - 8 packages @copilotkit/bot* -> @copilotkit/channels* (git mv dirs, names, workspace: cross-deps). Now includes @copilotkit/bot-intelligence -> @copilotkit/channels-intelligence (landed on main via #5761; unpublished, so renamed fresh with the family). - release.config.json scope keys + versionSource; ReleaseScope union; canary/stable-release/publish-release scope dropdowns; verify script - examples/slack (Kite) + examples/teams: deps, jsxImportSource, imports - showcase/shell-docs: content dirs docs/bots->docs/channels and reference/bot->reference/channels, nav registry, redirects createBot and other API names unchanged. Old @copilotkit/bot* to be deprecated after the new packages publish (bot-intelligence was never published). Re-derived onto latest main (was conflicting after #5761 landed). Refs OSS-438
2026-07-08 13:07:02 -05:00
"versionSource": "@copilotkit/channels",
chore(release): unify channels version scope
2026-07-14 22:45:42 -07:00
"sharedVersion": true
ci: add scope dropdown (monorepo, cli, angular) to release workflows Each release scope has its own packages, version source, and independent version track: - monorepo: 12 core @copilotkit/* packages (shared version) - cli: copilotkit CLI (independent version) - angular: @copilotkitnext/angular (independent version) Branch pattern is now release/publish/<scope>/v<version> and git tags use <scope>/v<version> for non-monorepo scopes.
2026-04-10 23:04:48 -07:00
}
}
ci: add bespoke stateless release system Replace changesets with a simple, stateless release system: Stable release (PR-gated): Actions → "create release PR" → pick patch/minor/major → CI runs → merge → publishes to npm, creates git tag + GitHub Release Prerelease (ad-hoc): Actions → "publish / prerelease" → publishes current version with -canary.<suffix|timestamp> to npm under "canary" tag Key features: - All 12 core @copilotkit/* packages share a single version - AI-generated release notes via Anthropic API - Notion draft for team editing before merge - Notion link commented on the release PR - Guards: concurrent release PR check, version > npm check, clean semver check, canary-only prerelease tag - release/publish/v* branch pattern (hard to accidentally match) - TypeScript throughout (tsx runner) - release.config.json with versionedTogether/versionedIndependently
2026-04-10 22:18:11 -07:00
}
Reference in New Issue Copy Permalink