Backend 7.1.1 build 0.0.2 - Full Changelog
Released 2026-09-23 · 3 issues · 1 feature · 2 fixes
The complete record: every commit in the release, grouped by type, including work that never reaches a customer-facing note. The external changelog is the readable summary of the same release.
Features
-
DEV-3100 - Angular project > Backend UI > Support HTTPS connection to ACS
Bug Fixes
-
Set release/7.1.1 component version to 7.1.1
The branch was cut without bumping docs/src/antora.yml, so it still declared version 7.1.2 with the same prerelease as master. Antora keys a component version by 'version' alone, so master and release/7.1.1 both resolved to 7.1.2@ft-ui-backend and collided on modules/ROOT/nav.adoc:
FATAL (antora): Duplicate nav in 7.1.2@ft-ui-backend
which fails the whole docs-portal build. Set the version to 7.1.1 to match the branch so it publishes as its own component version.
-
DEV-2767 - Angular Project > "ISP= 1/2" > Specific domain user > Settings > System settings > External system > Edit > An error occurred
Documentation
-
Restructure UI Backend deployment to unified style
Rewrite separate-host-deployment.adoc to document only the UI Backend service (Spring Boot REST API) following the FTACS installation skeleton. Portals and AI agent are now referenced as companions/prerequisites, not deployed here. Sync nav.adoc and index.adoc labels to the new H1. Add docs/decisions/LOG.md recording repo/env discrepancies.
-
Update antora version to 7.1.2 (dev)
-
Regenerate changelog for release 7.1.1
-
Regenerate changelog for release 1.0.4
-
Align nav with the ACS structure, rename the guide to Installation & Deployment
-
Unify structure, dependencies table and ClickHouse 26.2
-
Fix cross-references and residual consistency findings
-
Correct environment and mount facts
-
Enable section numbering to match the other install guides
-
Drop the Overview property table
No other install guide carries it and every fact it listed is stated in the section that owns it. The Spring Boot version, its only unique fact, moved to the runtime note.
-
Align Registry Authentication with the reference format
-
State the read-only registry credentials
Matches the other install guides, which publish the pull-only account values directly.
-
Set the install root by cd, not by exporting DATA_FOLDER
Compose writes every volume as ${DATA_FOLDER:-.}, so the working directory already fixes the mounts. An exported shell variable does not survive the next login shell and env_file does not feed interpolation.
-
Use the literal install root in copy-paste commands
-
Use the platform directory layout
The full-system deployment guide defines one directory per service directly under /usr/local/ft-system. Neither the ft-data level nor the ft-services root exists there; the divergence from the shipped compose and .env is recorded in docs/decisions/LOG.md.
-
Use one brace-expanded mkdir per service
Matches the layout command in the full-system deployment guide: create the service directory under /usr/local/ft-system and work from the stack root.
-
Document the platform directory layout and env file split
-
Fix defects found in the documentation audit
-
Correct the truncated shared backend keyword
The value must match FT_UI_BACKEND_KEYWORD in the deployed environment; the repository .env files ship ft12Internal#$Auth%^.
-
Use ft12Internal%^ as the shared backend keyword
-
DEV-2651 - Angular > OneIoT backend > Doc portal > Folder structure unification request
-
Fix version
-
Add changelog for 7.1.1 build 0.0.2 (backend)