v1.0.1 — Safer local-engine records

This patch release makes the local engine's record file safe under concurrent use and removes the SDK's handling of its retired package names. If you run several local-engine deploys or stops at once, they no longer undo each other's bookkeeping.

npm install @xano/sdk@1.0.1

Concurrent local-engine deploys and stops no longer lose each other's records

Every write to the local-engine record file read the whole file, changed one entry and wrote it back with nothing serializing it, so two concurrent processes could drop a record, a completed-import marker, or bring back a stopped engine's record. All writes now go through one lock.

local-engine stop --all keeps the record of an engine a concurrent deploy just started

stop --all cleared every record left after its stops, so a deploy that recorded its engine after the listing lost that record: the engine was then treated as foreign and a later --keep-data deploy saw it as unfilled. It now clears only records that named no running engine, and only if they are unchanged.

The SDK no longer handles its retired package names

The install-time refusal of modules built for the old SDK packages, and the changelog generator's notes about the earlier version lines, are removed. The SDK is @xano/sdk.