migration.out_of_date

The entities ask for a database schema that no migration has written yet, because they are new or have changed since the latest migration.

Area 5, Entities, stores and migrations; not declinable; the next step is usually the agent's.

Why Jadpo refuses it

Entities describe the tables you want, and migrations are the steps that take a real database there. jadpo check compares the two. When they disagree, a deploy would run code against tables that don't match it, so the check fails at once, in the editor, the build and CI, rather than when the code first reads a missing column.

What it looks like

A project with an entity and no migration yet:

domains/notes/entities/note.jadpo:

entity Note {    id: Uuid    body: Text}

  |1 | entity Note {  |        ^^^^ no table yet

(agent) at the end of the next: line means your coding agent can make the fix itself.

Once a migration exists, changing an entity raises the same error, naming what changed. Here pinned was added to Note after the first migration was written:

domains/notes/entities/note.jadpo:

entity Note {    id: Uuid    body: Text    pinned: Bool?}

  |1 | entity Note {  |        ^^^^ changed

How to fix it

If there is no migration yet, write the first one:

jadpo migrate new initial

  compared the entities with an empty database  Note    + table  note                      new entity  System tables    + table  jadpo_circuit_breakers    system table for circuit breakers    + table  jadpo_deliveries          system table for deliveries    + table  jadpo_handled_deliveries  system table for handled deliveries    + table  jadpo_housekeeping        system table for housekeeping    + table  jadpo_idempotency_keys    system table for idempotency keys    + table  jadpo_operator_actions    system table for operator actions    + table  jadpo_outbox              system table for outboxWrote database/migrations/20261020T1400_initial/    snapshot.json  the whole schema at this point    postgres.sql   14 statements: create table, add unique rule, add reference, create indexnext: jadpo check  confirms the migration matches the entities

The new folder holds the schema as the entities describe it and the SQL that creates it. jadpo migrate apply runs that SQL against a database as a deploy step.

If the entities changed since the latest migration, write the next one, named after what it does:

jadpo migrate new add_pinned

  compared the entities with 20261020T1400_initial  Note    + pinned  boolean  new fieldWrote database/migrations/20261020T1401_add_pinned/    snapshot.json  the whole schema at this point    postgres.sql   1 statement: add columnnext: jadpo check  confirms the migration matches the entities

The migration adds the pinned column. A change that needs a decision, such as a new required field, also writes a changes.jadpo to fill in (migration.decision_required).

Related

• Migrations
• migration.decision_required