v0.20.0

Fixed

A field marked lvt-upload-with that cannot reach the handler now says so. (#152, livetemplate/livetemplate#508)

Fields only ever travel on the multipart upload path:

Mode	Transport	Marked fields arrive?
Proxied	always multipart	Yes, always — OnUpload included
Volume	chunked over WebSocket; multipart when the socket is down	Only on the multipart fallback
Direct	presigned PUT, then a metadata-only completion	No, on any path

The chunked transport sends bytes and entry ids, and Direct completes with a metadata-only message — so the server builds the upload_<name>_complete action's context from an empty map and the handler sees nothing, with nothing in the markup to explain it.

The client now warns on both transports, naming the marked fields and the remedy — which differs by mode. Volume delivers them on its multipart fallback; Direct never delivers them at all, so its message points at controller state instead.

Nothing marked means no warning: a message on every chunked upload would train people to ignore it.

Internal

scripts/release.sh now runs tests and the build before touching VERSION, package.json or CHANGELOG.md, and restores those files if a run aborts before committing. Previously a failing test left them rewritten — and since the script refuses to start on a dirty tree, the next attempt failed for a reason unrelated to the first. (#151)

Version

This release jumps 0.19.1 → 0.20.0 to track the core library's v0.20.0, which scripts/release.sh enforces on major.minor.

Full changelog: https://github.com/livetemplate/client/blob/v0.20.0/CHANGELOG.md