Release Changelog

This section contains release changelogs automatically generated from Conventional Commits by the CI/CD Finalize-Sprint pipeline.

Release History

Changelogs are organized by release version under changelog/{version}/. A new version folder is published each time a release branch is finalized.

Each release contains:

File Description

qa.adoc

Jira ticket references only (refs: commits). Use this for QA tracking and verification.

external.adoc

Customer-facing changes: Jira refs, features, bug fixes, documentation, and maintenance.

all.adoc

Complete changelog including every conventional commit type.

External Components in a Release

Beyond the generated files, every release page (changelog/{version}/index.adoc) carries a hand-maintained External components in this release section: the versions of the third-party products this release was built and verified against — the relational database, ClickHouse, Hazelcast, the base image and the application framework.

That section is written by hand because the generated files cannot produce it: they are derived from commit messages, and a dependency that did not change in a sprint leaves no commit behind while still being part of what the release was verified against.

The current values live in Third-Party Components and are copied into the release page when the release is cut.

Once a release is published, those same third-party versions — and the versions of every other FT service shipped alongside — also appear on FT Version Control, together with the upgrade steps between releases. That page is the platform-wide record across services; the section here describes only what this branch is built against right now.

Add the section to changelog/{version}/index.adoc only. qa.adoc, external.adoc and all.adoc are regenerated in full by the Finalize-Sprint pipeline, and anything hand-written in them is lost on the next run.

Current values

What this branch is built and verified against right now, and the set that gets copied into the first release page when a release is cut. It describes the current state of the branch — not a released version.

Component Version Notes

Java

25

Language level and runtime (build.gradle)

Spring Boot

4.0.7

Web layer, JPA, Quartz scheduling, security, mail (build.gradle)

MySQL

8.4 (minimum)

ftacs, ftacs_quartz and ftacs_qoe_ui schemas; platform-wide minimum

Oracle

21c (minimum)

Same three schemas; platform-wide minimum

ClickHouse

26.2 (minimum)

QoE time-series store, reached over HTTP on 8123 — not the native TCP port 9000

Hazelcast

5.0 server minimum (5.3+ recommended), client library 5.5.0

Distributed cache the service joins as a client (build.gradle)

MySQL driver

com.mysql:mysql-connector-j (version managed by Spring Boot)

Bundled in the image

Oracle driver

com.oracle.database.jdbc:ojdbc11 (version managed by Spring Boot)

Bundled in the image

ClickHouse driver

com.clickhouse:clickhouse-jdbc 0.9.8

Replaced the retired com.github.housepower native driver (DEV-2736)

Base image

eclipse-temurin:25-jre-alpine

Runtime image the service is built from (Dockerfile)

Docker Engine / Compose

20.10+ / 2.0+

Only supported deployment method

Changelog Format

Entries are derived from the commit message prefix:

Prefix Section

feat

Features

fix

Bug Fixes

perf

Performance

docs

Documentation

refactor

Refactoring

chore

Maintenance

refs: DEV-XXXX

Jira References (rendered as clickable links)

Example commit messages:

feat(dashboard): add per-group KPI drill-down
fix(clickhouse): read name_ids_in_formula as Object[] on the official driver
docs(installation): document the third-party component versions
refs: DEV-2736

Releases

No release has been published for this component yet — the Finalize-Sprint pipeline has never run for it, so there is no changelog/{version}/ folder and no generated qa.adoc / external.adoc / all.adoc trio. Released versions will be listed here once a release branch is finalized, each carrying the external-component versions from Current values.

Until then the per-build change list lives in release_notes.txt at the root of the repository, where each entry names the Jira issues closed in that build.