QA Changelog 1.0.3

Released 2026-09-04 · v7.1.2.a · 3 issues

For test planning. Lists every Jira issue in the release together with the maintenance work that came with it. What those issues mean for a customer is in the external changelog.

Jira References

  • DEV-1933 - Angular Project > USP > No Mesh > Client via Wi-Fi > Wi-Fi management plus > "Network topology" cube > Incorrect "RSSI" value

  • DEV-2281 - Angular Project > TR-181 > Wi-Fi management plus > Dataelement / MultiAP > Network connected clients > Client with "Undefined" status is absent

  • DEV-2551 - Angular project > Support portal > Wi-Fi management plus > Gateway Wi-Fi status cube > A false warning

Chores

  • Update docs

  • Add deployment.yaml contract for Deployment Manager

    Deployment Manager reads this file from the tip of this branch to know the service’s image, ports, volumes, clustering pattern and the variables an operator must fill in. It was previously vendored in ft-internal-tools (deployment-manager/catalogue/contracts/ft-device-network-service.yaml); this repository now owns it.

  • Add the deployment/ config tree Deployment Manager mounts

    These are the application config files a generated Compose bundle mounts into this service’s container. They were vendored in ft-internal-tools (deployment-manager/catalogue/services/); this repository now owns them, and Deployment Manager reads them from the tip of this branch.

    Private key material is deliberately NOT here: keys and keystores stay in the one place they already live and are laid over this tree at generation time, so the same private key does not gain a copy per repository.

Dependencies

  • ACS → FT Configs Service v1.0.2-b0.0.1

  • UI Backend → ACS v7.1.2-b0.0.1

  • UI Portals → UI Backend v7.1.2-b0.0.1

  • FT Device Network → ACS v7.1.2-b0.0.1

  • UI AI Agent → UI Backend v7.1.2-b0.0.1

  • UI AI Agent → FT Device Network v1.0.3-b0.0.1

See also