Upgrade Kumiko dependencies

Standard workflow when bumping @cosmicdrift/kumiko-* deps in an app. Prevents deploying app code that expects new columns against an old DB schema.

Applies to: any app with @cosmicdrift/kumiko-bundled-features (publicstatus, kumiko-studio, customer apps).

Tooling (2026-05): Bun for install/test/build/CLI. Schema migrations live under kumiko/migrations/; reference layout is kumiko-framework/samples/apps/use-all-bundled/kumiko/schema.ts.

Run all kumiko … commands from the app directory (CLI uses INIT_CWD):

cd <app>
bun ../kumiko-framework/bin/kumiko.ts <command> …

TL;DR

cd <app>
bun install
bun ../kumiko-framework/bin/kumiko.ts schema generate bump-0-18-0
git diff kumiko/migrations/
cd .. && bun check && cd <app> && bun test
git add kumiko/migrations/ package.json bun.lock
git commit -m "chore: bump kumiko + schema migration"
git push

Deploy: kumiko schema apply (pre-deploy step, not app boot).

Bump all five packages together

@cosmicdrift/kumiko-framework
@cosmicdrift/kumiko-bundled-features
@cosmicdrift/kumiko-dev-server
@cosmicdrift/kumiko-renderer
@cosmicdrift/kumiko-renderer-web

For 0.x releases, caret ranges may not cross minor bumps — edit package.json explicitly, then bun install and commit bun.lock.

See also

• kumiko schema — schema migration CLI
• Features and composition — how bundled features mount