v0.45.0

New Features

• Preview of more detailed memory reporting. Memory is judged on its average over the last 60 seconds, and a degraded status names the cause: the container's memory limit, the machine's memory, processes waiting for memory, or a process stopped because memory ran out. Turn it on with USE_FSMV2_MEMORY_MONITOR=true and recreate the container

Improvements

• A write flow can now only subscribe to topics beneath the location of its own bridge, so a bridge at enterprise.site.line no longer reads data from elsewhere in the hierarchy. Existing write flows that subscribe outside their location stop writing after the upgrade and name the offending topics in the bridge's status, and the bridge's read flow keeps running while the topics are corrected
• Each write flow topic must now name one existing data contract, such as umh.v1.enterprise.site.line._historian.*, instead of covering every contract of a location at once. Accepted contracts are _raw, _historian, and the ones listed under dataContracts:, so a typo no longer silently subscribes to nothing. Existing write flows whose topics name no contract, or one that does not exist, stop writing after the upgrade and the bridge's status names the offending topics alongside the contracts they may use
• Setting the environment variable BYPASS_WRITE_FLOW_VALIDATION=true lets existing write flows keep running while their topics name a data contract that is not declared under dataContracts: or has no version, such as _mes_order. Use it to migrate write flows to the new topic rules without stopping them. The bridge then reports degraded and its status names the offending topics. All other topic rules still apply

Fixes

• A bridge deploy now fails within seconds when benthos rejects the configuration before it starts, for example a misspelled setting (field retension not recognised). The error names every rejected setting at once. The bridge is kept and only the rejected flow is stopped. Before, the deploy waited 30 seconds and failed without naming the setting
• Deploying or editing a stand-alone flow, or editing a bridge, with a configuration benthos rejects now shows the benthos error instead of "check the component logs"
• Connection checks now exclusively use FSMv2. NMAP_BACKEND is ignored and can be removed from configuration; the FSMv1 fallback is no longer available.
• Updated golang.org/x/net to v0.62.0 in the umh-core binary to patch CVE-2026-78661, where crafted HTML makes parsing use excessive resources, and CVE-2026-97045, where rendering HTML could break out of raw text.