External Changelog

Release: v7.0.4

Breaking Changes

  • update deployment requirements

BREAKING CHANGE:
* clean IOTW installation is now required
* FTDeviceNetworkService must be updated
* clickhouse_update_6.0.221.sql must be applied

Jira References

Features

Bug Fixes

  • improve FTP host parsing, enhance validation logic, and refactor file server status checks

Documentation

  • add antora changelog for release 7.0.4_0.0.10

  • add changelog for release 7.0.4_0.0.10

  • add antora changelog for release 7.0.4_0.0.10

  • add changelog for release 7.0.4_0.0.10

Chores

Docker Images

For Transfer Image to Offline Server steps below, an explicit --platform matching the offline target server’s architecture is required. The images in Harbor are multi-arch (linux/amd64, linux/arm64); without --platform, docker pull selects the host architecture, which may not match the target. For example, on an Apple Silicon (arm64) Mac without --platform, the resulting archive will be arm64 and will fail with a platform does not match warning on amd64 servers. The examples use linux/amd64; replace it with the platform of your offline target server (linux/arm64, etc.).

backend

Image: hub.friendly-tech.com/ui/backend:7.0.4

SHA256: sha256:f0fa1ad67390ff74a6977994ed6d2365a0805ca5b3e0d76291eb6f516165e36e

Pull from Registry

docker pull hub.friendly-tech.com/ui/backend:7.0.4

Transfer Image to Offline Server

On a machine with Harbor access, pull the image for the target server’s architecture and export it:

docker login hub.friendly-tech.com
docker pull --platform linux/amd64 \
  hub.friendly-tech.com/ui/backend:7.0.4
docker save hub.friendly-tech.com/ui/backend:7.0.4 \
  -o backend-7.0.4.tar
gzip backend-7.0.4.tar

Transfer backend-7.0.4.tar.gz to the offline server (e.g., via scp or removable media), then load it:

gzip -dc backend-7.0.4.tar.gz | docker load

Portals

Image: hub.friendly-tech.com/ui/portals:7.0.4

SHA256: sha256:ee39f1bc096a7308775c84814fe53f488484ba927421c6ad90bcf46b31e198d5

Pull from Registry

docker pull hub.friendly-tech.com/ui/portals:7.0.4

Transfer Image to Offline Server

On a machine with Harbor access, pull the image for the target server’s architecture and export it:

docker login hub.friendly-tech.com
docker pull --platform linux/amd64 \
  hub.friendly-tech.com/ui/portals:7.0.4
docker save hub.friendly-tech.com/ui/portals:7.0.4 \
  -o portals-7.0.4.tar
gzip portals-7.0.4.tar

Transfer portals-7.0.4.tar.gz to the offline server (e.g., via scp or removable media), then load it:

gzip -dc portals-7.0.4.tar.gz | docker load

AI Agent

Image: hub.friendly-tech.com/ui/ai-agent:1.0.2

SHA256: sha256:81d7e81f273cc67355063e1193ed6c7c1c75797e801450880a2ef2dc4b30998d

Pull from Registry

docker pull hub.friendly-tech.com/ui/ai-agent:1.0.2

Transfer Image to Offline Server

On a machine with Harbor access, pull the image for the target server’s architecture and export it:

docker login hub.friendly-tech.com
docker pull --platform linux/amd64 \
  hub.friendly-tech.com/ui/ai-agent:1.0.2
docker save hub.friendly-tech.com/ui/ai-agent:1.0.2 \
  -o ai-agent-1.0.2.tar
gzip ai-agent-1.0.2.tar

Transfer ai-agent-1.0.2.tar.gz to the offline server (e.g., via scp or removable media), then load it:

gzip -dc ai-agent-1.0.2.tar.gz | docker load