What it is
fz.
fz links against your venture's compiled-in harness and runs as a bin target inside the venture repo, which is the pattern the venture template ships. That is not packaging preference: a migration collector that guessed at your module list would collect the wrong migrations, and a doctor that guessed at your ports would pass a venture that cannot boot.
fz migrations collect walks the modules in config order and writes files named so that wrangler d1 migrations apply executes them in the right order. The lock file is the part that matters: migrations/.harness-lock.json pins each module/migration-id to its global file name plus a sha256 of its content, so a migration edited after it shipped is a failure rather than a silent divergence between two databases.
Ports
tool — runs outside the request path
Commands
migrations collect, migrations apply, doctor, modules, data export, data import
History
Changelog.
From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 8 versions recorded, newest first. Every published version is on crates.io.
Other
- update Cargo.lock dependencies
Other
- updated the following local packages: cratefield-core, cratefield-runtime-native, cratefield-adapter-sqlite, cratefield-adapter-postgres, cratefield-push-auth, cratefield-adapter-typesafe, cratefield-adapter-webpush, cratefield-push-wiring, cratefield-client-ts, cratefield-import-supabase, cratefield-tables, cratefield-introspect
6 earlier versions 0.4.0 to 0.7.0
Other
- fz doctor: fail on module SQL a venture's dependencies ship but no module declares (migration-not-declared) (#872)
Other
- update Cargo.lock dependencies
Other
- update Cargo.lock dependencies
Changed
- Breaking: requires
cratefield-core0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).
Added
- Breaking: requires
Other
- Route policy: let one module declare a signature verifier per webhook route (#595) (#632)
- Production readiness fails when a module declares RateLimiter and none is mounted; a missing Workers limiter binding fails closed (#562) (#569)
- Verify the cratefield-core 0.6.0 release round (#558) and fix a stale client-ts comment in the CLI manifest (#566)
Postgres is applied directly, tracked idempotently in harness_migrations.