spacetimedb-upgrade

Stars13

Forks2

UpdatedJune 19, 2026 at 06:39

Use when migrating from SpacetimeDB 1.0 to 2.0 or fixing code affected by 2.0 breaking changes. Covers reducer callbacks, event tables, event type changes, subscription API, table accessor naming, database-name connections, `sender()` method, update methods, scheduled functions, private codegen, light mode, `CallReducerFlags`, and confirmed reads. Triggers on: upgrade, migrate, 1.0, 2.0, breaking changes.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

DanMossa

DanMossa/spacetimedb-skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	spacetimedb-upgrade
description	Use when migrating from SpacetimeDB 1.0 to 2.0 or fixing code affected by 2.0 breaking changes. Covers reducer callbacks, event tables, event type changes, subscription API, table accessor naming, database-name connections, `sender()` method, update methods, scheduled functions, private codegen, light mode, `CallReducerFlags`, and confirmed reads. Triggers on: upgrade, migrate, 1.0, 2.0, breaking changes.
license	MIT

Use this skill for SpacetimeDB 1.0 to 2.0 migration work.

Core migration checks

Reducer callbacks changed. Prefer event tables for durable, subscribable result notifications; use per-call _then() style callbacks only when the guide's limitations are acceptable.
Event types changed. Update client event handling before assuming old reducer-result event shapes still exist.
Subscription APIs and table accessor names changed. Regenerate bindings and update calls to the generated names rather than patching guessed identifiers.
Clients connect by database name or identity, not the old module naming assumptions.
In Rust and C++, sender is now a method: use ctx.sender(). TypeScript and C# property syntax is unchanged.
Only primary keys get generated update methods. For other changes, update through the primary-key index or delete and insert when the primary key changes.
Scheduled functions, private codegen, light mode, CallReducerFlags, and confirmed reads all have separate migration notes. Load the guide section before editing those areas.

Reference map

Need	Open
Migration guide and checklist	references/upgrade.md

Guidance

Identify the exact breaking change before editing code; the guide has separate remedies for callbacks, events, subscriptions, table naming, connection names, sender, updates, scheduling, codegen, light mode, flags, and confirmed reads.
Prefer event tables over old reducer callback patterns when the guide recommends them.
Check generated client APIs after changing module names, table accessors, visibility, or private items.

More from this repository

same repository

spacetimedb-databases

DanMossa/spacetimedb-skills

Use when creating, developing, building, publishing, migrating, or reasoning about SpacetimeDB database modules. Covers local development, module build/publish flow, transactions, automatic migrations, incremental migrations, and the database cheat sheet. Triggers on: database module, spacetime publish, build module, migration, transaction, atomicity, developing module.

2026-06-1913

spacetimedb-reducers

DanMossa/spacetimedb-skills

Use when writing SpacetimeDB reducers, lifecycle reducers, scheduled reducers, reducer context code, table mutations, indexed lookups, reducer isolation logic, or reducer error handling. Triggers on: reducer, ReducerContext, ctx, sender, client_connected, client_disconnected, init, scheduled reducer, insert row, delete row, update row.

2026-06-1913

spacetimedb-auth

DanMossa/spacetimedb-skills

Use when implementing SpacetimeDB authentication or authorization, including SpacetimeAuth, Auth0, Clerk, OIDC, auth claims, subject/issuer checks, custom claims, roles, row-level security, and rejecting client connections. Triggers on: auth, authentication, authorization, SpacetimeAuth, Auth0, Clerk, OIDC, claims, RLS, row-level security.

2026-05-0713

spacetimedb-cli

DanMossa/spacetimedb-skills

Use when running or explaining SpacetimeDB CLI commands and standalone configuration. Covers `spacetime init`, `build`, `publish`, `generate`, `call`, `sql`, `logs`, `describe`, `dev`, `server`, `start`, login/logout, and `config.toml`. Triggers on: spacetime CLI, spacetime publish, spacetime generate, spacetime sql, spacetime logs, spacetime server.

2026-05-0713

spacetimedb-client-c-sharp

DanMossa/spacetimedb-skills

Use when writing SpacetimeDB C# or Unity clients, generated C# bindings, connection setup, subscriptions, cache access, reducer invocation, callbacks, or identity handling. Triggers on: C#, CSharp, Unity, C# SDK, generated C# bindings, Unity SDK, C# subscription, C# reducer call.

2026-05-0713

spacetimedb-client-rust

DanMossa/spacetimedb-skills

Use when writing SpacetimeDB Rust clients, generated Rust bindings, connection code, subscriptions, cache access, reducer invocation, callbacks, or identity handling. Triggers on: Rust client, Rust SDK, generated Rust bindings, Rust subscription, Rust reducer call, Rust callbacks.

2026-05-0713

name	spacetimedb-upgrade
description	Use when migrating from SpacetimeDB 1.0 to 2.0 or fixing code affected by 2.0 breaking changes. Covers reducer callbacks, event tables, event type changes, subscription API, table accessor naming, database-name connections, `sender()` method, update methods, scheduled functions, private codegen, light mode, `CallReducerFlags`, and confirmed reads. Triggers on: upgrade, migrate, 1.0, 2.0, breaking changes.
license	MIT

Use this skill for SpacetimeDB 1.0 to 2.0 migration work.

Core migration checks

Reducer callbacks changed. Prefer event tables for durable, subscribable result notifications; use per-call _then() style callbacks only when the guide's limitations are acceptable.
Event types changed. Update client event handling before assuming old reducer-result event shapes still exist.
Subscription APIs and table accessor names changed. Regenerate bindings and update calls to the generated names rather than patching guessed identifiers.
Clients connect by database name or identity, not the old module naming assumptions.
In Rust and C++, sender is now a method: use ctx.sender(). TypeScript and C# property syntax is unchanged.
Only primary keys get generated update methods. For other changes, update through the primary-key index or delete and insert when the primary key changes.
Scheduled functions, private codegen, light mode, CallReducerFlags, and confirmed reads all have separate migration notes. Load the guide section before editing those areas.

Reference map

Need	Open
Migration guide and checklist	references/upgrade.md

Guidance

Identify the exact breaking change before editing code; the guide has separate remedies for callbacks, events, subscriptions, table naming, connection names, sender, updates, scheduling, codegen, light mode, flags, and confirmed reads.
Prefer event tables over old reducer callback patterns when the guide recommends them.
Check generated client APIs after changing module names, table accessors, visibility, or private items.