|
1 | 1 | # Changelog |
2 | 2 |
|
| 3 | +## 1.1.0 (2026-07-13) |
| 4 | + |
| 5 | +The FX connection manager — hypernova learns OPC UA FX (Parts 80/81): |
| 6 | + |
| 7 | +- **`hypernova fx connect`** wires one FX server's output dataset to another's |
| 8 | + input dataset at runtime: publisher side first, its returned wire |
| 9 | + coordinates handed to the subscriber side as the peer; on subscriber refusal |
| 10 | + the publisher side is closed again (no half-open links). |
| 11 | +- **`hypernova fx status`** browses a server's live `ConnectionEndpoints`; |
| 12 | + **`hypernova fx close`** tears a connection down by id. |
| 13 | +- **`--register / --register-as / --network`** turn the established stream into |
| 14 | + a first-class hypernova publication — field names *and types* read from the |
| 15 | + publisher's FX view — so an engineered link shows live in the registry |
| 16 | + browser alongside ad-hoc consumers on the same wire. |
| 17 | +- Targets any server exposing the FX pattern; today that is |
| 18 | + [supernova >= 1.2.0](https://github.com/quasarnova-team/supernova) with an |
| 19 | + `<Fx>` configuration section. Requires the `[bridge]` extra (asyncua). |
| 20 | +- 5 new unit tests (publisher-first ordering, coordinate handoff, rollback on |
| 21 | + subscriber refusal, projection type map) — 87 tests total, green. Verified |
| 22 | + end to end against real supernova servers in all four backend combinations; |
| 23 | + registry synergy checked live (typed registration + the registry's message |
| 24 | + counter climbing on the FX stream). |
| 25 | + |
| 26 | +The core (registry, clients, relay, bridges, signing) is unchanged — 1.1.0 is |
| 27 | +purely additive. Docs: [doc/fx.md](doc/fx.md). |
| 28 | + |
3 | 29 | ## 1.0.0 (2026-07-12) |
4 | 30 |
|
5 | 31 | The consolidation release — every v0.1 gap closed: |
|
0 commit comments