- Add package.json exports for v2/{express,hono,node} subpaths
- Add elysia devDependency and tsdown entry points
- Exclude bun integration tests from vitest config
- Update CI workflows to include runtime-servers test job
- Add runtime-server-adapter docs page
- Add changeset for the fetch-based runtime feature
Flatten all packages from packages/v1/* and packages/v2/* into packages/* —
every package now lives directly under the @copilotkit/ scope with no v1/v2
subdirectories.
- Move all v1 packages (react-core, react-ui, runtime, shared, etc.) from
packages/v1/* to packages/*
- Absorb v2 react code into packages/react-core/src/v2/ (exported via /v2 subpath)
- Absorb v2 agent code into packages/runtime/src/agent/ (exported via /v2 subpath)
- Move v2 packages (core, angular, demo-agents, etc.) to packages/*
- Replace all @copilotkitnext/* imports with @copilotkit/* equivalents
- Keep @copilotkitnext/angular as the sole exception (angular remains on next)
- Update CI workflows, renovate config, release scripts for flat structure
- No public API surface changes — all exports fields are preserved
Co-authored-by: Alem Tuzlak <t.zlak@hotmail.com>
Signed-off-by: Tyler Slaton <tyler@copilotkit.ai>
Add sdk-python/** to the e2e_dojo workflow path filter so Python SDK
changes actually get tested. A detect-changes job uses dorny/paths-filter
to distinguish TS vs Python changes — when only sdk-python/** changed,
only the needs_python suites run (11 of 15). TS/workflow/changeset
changes still trigger all suites as before.
Most dojo e2e suites (langgraph, agno, crew-ai, pydantic-ai, etc.)
run Python agents that use the sdk-python package, but the workflow
path filter didn't include sdk-python/**, so changes to the Python
SDK never triggered e2e tests.
Parallel CI workflows were each getting a different Nx Cloud execution
ID, resulting in separate CIPEs instead of one unified view. Set a
stable NX_CI_EXECUTION_ID env var using head_ref + sha + run_attempt
so all workflows for the same push are grouped together. Also add
NX_CI_EXECUTION_ENV per workflow to create labeled tab sections in the
Nx Cloud CIPE page.
prep-dojo-everything.js runs `pnpm install --no-frozen-lockfile` for the
dojo target, which resolves @copilotkit/* from the npm registry. When
link-cpk runs before prep-dojo, the symlinks it creates get overwritten.
Swapping the order ensures prep-dojo installs first, then link-cpk
overwrites the registry packages with local CopilotKit build outputs.
Update e2e_dojo.yml to pass CopilotKit/packages instead of
CopilotKit/packages/v1, so the updated ag-ui link-cpk.js script
links both V1 and V2 packages in dojo e2e tests.
Alem Tuzlak