v0.4.2

0.4.2

Reference. What this release does, what it does not, and what is simulated.

Is your plant on PostgreSQL? Then upgrade, and run one command. Every
PostgreSQL plant on 0.3.0, 0.3.1, 0.4.0 or 0.4.1 has a Maintenance screen that
never loads: it says "reconnecting…" for good, and no maintenance work is
handed out. After the upgrade:

fsmes init-db --pack packs/yourplant    # or, for a plant in a fleet: fsmes init-db --plant yourplant

On SQLite (the default, and every fsmes demo) there is nothing to run
and nothing is lost: those plants never had the fault.

Released: 2026-10-26. Previous: 0.4.1, on PyPI 2026-10-25.

---

What 0.4.2 is

The Maintenance screen works on PostgreSQL again. Early migrations made
nine status columns a closed list of words PostgreSQL itself enforces. 0.3.0
added the word assigned to maintenance work, and no migration told the
database, so it refused the word: /maintenance/due answered 500, the screen
never filled, and the dispatcher could not assign anyone. One migration,
2c6e817b9faf, makes those columns plain text, as the code always declared
them, and keeps every stored word. A test now builds the schema the way a
plant does, on PostgreSQL, and fails on any word the database would refuse.

Every header dot tells the truth. The AI tab's said "connecting…"
forever; it says "live" now. Six screens' grey "live" dots are green.

The Orders page opens with the New-order form closed, not open on every visit.

What 0.4.2 does not do, and what is simulated

Nothing in the plant is new, so everything 0.4.0 does not do stands
word for word — no PLC write path, no redundant SQLite, no database failover, no
chat across a takeover, the kill proven on Linux only, no real plant anywhere —
and a number still comes from the line simulator in src/fsmes/sim/ over OPC UA.

Upgrading from 0.4.1

pipx upgrade factorysemantics-mes          # or py -m pip install --upgrade
fsmes --version                            # 0.4.2
fsmes init-db   --pack packs/yourplant     # b6f0c2a71d58 -> 2c6e817b9faf
fsmes db-status --pack packs/yourplant     # "at the current schema"

The plant may stay up while init-db runs: small tables, each locked for a
moment. The backup, the fleet form and what was tried are on
upgrading between versions.

---

Every change in this release: CHANGELOG.