The changesets/action@v1 writes auth to ~/.npmrc but
actions/setup-node sets NPM_CONFIG_USERCONFIG to a temp path,
causing pnpm to read a different .npmrc during publish. All packages
fail with E404 on PUT because the auth token isn't picked up.
This adds an explicit `npm config set` step that writes the literal
token to whichever file NPM_CONFIG_USERCONFIG points at.
https://claude.ai/code/session_01KnUcvcGEthP64SKk98HzJ6
- 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
Replace eslint and prettier with oxlint and oxfmt for faster linting
and formatting across the monorepo. Remove all eslint and prettier
configs, dependencies, and related packages. Add .oxlintrc.json and
.oxfmtrc.json for the new tooling. Update CI workflows and lefthook
hooks accordingly. Reformat codebase with oxfmt.
https://claude.ai/code/session_01GMkSf29p78HuMR1mbXn8He
- Add fail-fast: false to unit test matrix strategies so one Node
version failing doesn't cancel all other matrix jobs
- Add retry: 2 to runtime-client-gql vitest config (Nx confirmed
this package's tests as flaky during parallel execution)
- Replace fragile setTimeout waits in middleware express tests with
vi.waitFor() polling, which is resilient to CI timing variance
https://claude.ai/code/session_01W2Kb2HXsjZett3HdqM9zay
Add CopilotKit/demo as CODEOWNER for examples/showcases/ alongside
the existing dev team for reviewer auto-assignment.
Add a workflow that checks Demo team membership, verifies all changed
files are under examples/showcases/, then auto-approves and enables
auto-merge. PRs touching anything outside showcases or from non-Demo
members sit for normal review.
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>
These 8 workflows install uv but never invoke it. Only e2e_dojo.yml
actually needs uv (the dojo scripts use uv sync/run for Python agents).
Removing the unnecessary step saves CI time and reduces confusion.
## Summary
- **`.gitignore`** — add patterns for common binary extensions (`.exe`,
`.dll`, `.so`, `.dylib`, `.o`, `.obj`, `.a`, `.lib`, `.wasm`, `.dSYM/`)
- **CI workflow** (`static_check-binaries.yml`) — runs on all PRs to
`main`, checks for binary file extensions, `build/` directories,
`.dSYM/` directories, and individual files over 1 MB
- **Lefthook pre-commit** (`check-binaries`) — mirrors the CI check
locally, catching binary artifacts, build outputs, and oversized files
at commit time before they reach CI
Prompted by ag-ui PR #29 where ~15 MB of compiled macOS binaries were
accidentally committed. This adds the same protection to CopilotKit.
## Test plan
- [ ] Verify `.gitignore` additions don't affect existing tracked files
- [ ] Confirm the `static / check binaries` workflow runs and passes on
this clean PR
- [ ] Verify lefthook `check-binaries` fires on `git commit` and blocks
binary/oversized files
Fixes#2066
## Problem
`copilotkit_customize_config(config, emit_messages=False)` does not work
— TEXT_MESSAGE_* events are still emitted despite the configuration.
## Root Causes
1. **Metadata Reading Bug**: `getattr(raw_event, 'metadata', {})` always
returns `{}` because `raw_event` is a dict, not an object. Must use
`.get()` instead.
2. **Encoder Crash Bug**: Filtered events return `""` (empty string),
which gets yielded to the event encoder that expects objects with
`model_dump_json()`, causing `AttributeError`.
## Solution
1. Read metadata with `.get()` for dicts, `getattr()` for objects
2. Return `None` instead of `""` for filtered events
3. Override `run()` to strip `None` values before they reach the encoder
## Tests & CI
- Added 8 unit tests covering both bugs, pass-through cases, and `run()`
filtering
- Added `test_unit-python-sdk.yml` CI workflow — first-ever Python SDK
unit test coverage
- Added `pytest` as a dev dependency
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.
Add .gitignore patterns for common binary extensions (.exe, .dll, .so,
.dylib, .o, .obj, .a, .lib, .wasm, .dSYM) and a CI workflow that
checks all PRs for binary files, build directories, and files >500KB.
Prompted by ag-ui PR #29 where ~15MB of compiled binaries were
accidentally committed.
Jordan Ritter