Release history
Release notes
The releases that have been published and what each one brought. From 1.3.0 onwards updates are automatic: the installation checks a signed release announcement every day, verifies the package, installs it, and rolls back to the previous version if the health check does not pass. Details: Updates.
1.4.1 current
10.09.2026
- The product and documentation site went live at
tcmbkur.erp.tr; the package and the installation guide download from stable links. - Quote and contact addresses updated.
- The installation guide was expanded: all six wizard steps are now documented with screenshots.
1.4.0 licensing
10.09.2026
- Automatic licence registration. The installation identifies itself to the licence centre with a protected install identity; the customer no longer types a key.
- The wizard's licence step shows a short setup code and a QR code; the administrator makes the pairing centrally. Until the assignment arrives the screen reads "Waiting for licence assignment".
- The licence gates only the step that writes to Logo; fetching rates, the panel and updates work regardless of licence state.
- The customer installation package was simplified; installation is a single script.
1.3.0 automatic updates
09.09.2026
- Automatic updates are live. The updater lives outside the application under
%ProgramData%\ErpUpdate\TCMBKURand is triggered by a task that runs daily at 03:20 with SYSTEM rights. - A package is announced with a signed manifest; no file changes before its size and SHA-256 are verified.
- After installation there is a health gate: is the service running, does
/healthzreturn 200, does the reported version match the target. If it fails, the previous version is restored and the bad package is quarantined. - The database,
appsettings.Production.json,keys,logsandlisten-url.txtare preserved across updates. - The licence and device identity moved outside the application folder — an update no longer drops the identity.
1.2.1
09.09.2026
- The quote / contact address became configurable.
- The wording on the licence status screen was clarified.
1.2.0 licensing
09.09.2026
- Connection to the central licence service (
lisans.erp.tr). The decision arrives signed and is cached. - A network outage does not lock the application; it keeps working on the last valid cached decision.
- Licence status became visible in the panel.
Before 1.2.0
The core capabilities of the product were built in these releases:
| Area | What it brought |
|---|---|
| TCMB bulletin calendar | Finding the correct bulletin for a target day, walking back when there is none, and early-fetch protection (no writing of incomplete data before 15:30). |
| Logo mapping | Mapping RATES1..4 to foreign-exchange and banknote buying/selling, target-day selection, and the 16:00 check report. |
| Local installation model | The application runs as a Windows service on the customer's own machine; rate data never leaves it. |
| Setup wizard | Six-step installation: database, Logo connection, fetching rates, e-mail, licence and summary. |
Release policy
- Security patches are independent of licensing. An installation whose licence has expired still receives the patch.
- The schema only grows. A new version can read old data; a destructive change is spread across three releases.
- There is no downgrade. The only way back is the automatic rollback of a failed update.
- Every release's number and date appear in the footer of the panel and in the
/healthzresponse, from the same source.