# Release procedure
## Release versions
Workspace package versions for the 0.3.2 release preparation (not yet published):
| che-orm-macros | 0.3.2 |
| che-orm | 0.3.2 |
| che-sync-protocol | 0.1.0 |
| che-sync | 0.1.0 |
`che-orm-examples` is private (`publish = false`). Package the four public
crates explicitly rather than using `cargo package --workspace`.
The 0.3.2 patch releases core and macros together. It adds app-prefixed table-name
inference from literals or shared constants, and updates the template with
`createapp`, single/modular layouts and explicit migration generation.
The template requires 0.3.2; use local patches until publication.
Sync package versions remain unchanged; their archive
checks are workspace compatibility checks, not instructions to republish them.
The 0.3 ORM release introduces async database access with feature-selected
SQLite/PostgreSQL backends and role-aware synchronization. Shared models use
`#[orm(sync)]`, with `SchemaSet::client_model` or `server_model` selecting their
database role. Prefer [protocol-2 model journals](model-sync.md) for new clients;
their independent `pull`/`flush` methods have no snapshot phase. The
[scoped compatibility API](sync.md) retains explicit `full_load` and its own
history/upgrade rules. Both contracts require persistent server history;
replacement/history rewind is outside them.
## Verification
The `Release checks` workflow verifies SQLite, live PostgreSQL, Rust 1.88 and
the contents of the publishable archives. Run the equivalent checks locally
before tagging. SQLite and PostgreSQL are mutually exclusive features.
```bash
cargo fmt --check
cargo test --workspace --locked
cargo doc --workspace --no-deps --locked
cargo run -p che-orm-examples --bin manage --locked -- schema
cargo run -p che-sync --example offline --locked
python3 scripts/check-template.py
cargo +1.88.0 check --workspace --all-targets --locked
cargo +1.88.0 check -p che-orm -p che-sync --all-targets --locked --no-default-features --features postgres
cargo package -p che-orm-macros -p che-orm -p che-sync-protocol -p che-sync --locked
```
Set `TEST_POSTGRES_URL` to a disposable PostgreSQL database, then run the four
PostgreSQL commands in the workflow, including ignored runtime/model-role and
`model_log_postgres` tests. The latter verifies protocol-2 journals, concurrent
commits, no-op suppression, deferred FK projection and SET NULL.
For a local working tree review, packaging can use `--allow-dirty`; the release
must include the reviewed new source and test files in its commit.
Validate the matching downstream `che-rest` checkout with:
```bash
cargo test --test sync --test model_sync --test sync_lifecycle
cargo test --features sync-http
```
The matching che-tauri client and Todo application are separate downstream
workspaces. When changing sync contracts, also run their checks listed in the
[protocol-2 guide](model-sync.md#verification). Desktop compilation and the
two-client HTTP test do not replace manual GUI or deployment migration review.
For an existing installation, rehearse its compiled follow-up migration on a
copy of its database. Verify revisions, scope ownership, UUIDs, tombstones,
receipts, cursors and pending edits as described in [sync.md](sync.md) and the
[protocol-2 migration guidance](../../che-rest/docs/model-sync.md#rehearsing-an-existing-installations-migration).
Fresh-database tests do not validate this application-specific upgrade.
## Publication
Commit the verified release, then publish in dependency order. Wait for each
dependency to become available in the registry before publishing its consumers:
```bash
cargo publish -p che-orm-macros
cargo publish -p che-orm
python3 scripts/check-template.py --published
```
After registry verification, create the release tag `v0.3.2`. Publish sync crates
separately only when making a versioned sync release.
`cargo publish --dry-run -p PACKAGE` can be used before each step once its
dependencies are available. The multi-package `cargo package` check above
validates the release together using Cargo's temporary package registry even
before those dependencies have been published.