A version number is not decoration in the title bar. It is a promise: client and server understand each other the same way. That is why releases are run strictly.

How a release happens

One release is one tag in the repository. Every build comes from it: Windows, macOS (Apple Silicon and Intel) and Linux. The source is shared; only the packaging differs.

Each build passes its smokes on its own system: forty panel screenshots in two languages and two skins, the self-test, the version-title check, the crash-report check. A red smoke means no release.

The finished build is published together with its SHA-256 sum. The sum is computed from the contents of the file and shown on the download page for each system: that is how you confirm you downloaded what we built.

Why only the current version is available

The terminal checks its version against the site on launch, and an outdated copy refuses to run. An old file kept in an archive would therefore be dead weight: downloadable, not runnable.

The history of versions is still kept and shown — what changed is visible on the download page and below.

Released versions

1.0.2 — 21 September 2026

• The terminal reports its own crash: the report goes to the site on the next launch
• The idea review chart no longer stays on the previous timeframe
• The window title spells the version in full

1.0.1 — 20 September 2026

• Trade result in pips, percent of account and R — switchable in the linked-trades header
• Trade evidence inside someone else's idea: with a public profile outsiders see it, never in currency
• The review flag is carried honestly: unknown means the terminal stays silent instead of ticking a box
• The window title spells the version in full: it read “v1.0” while running 1.0.1

1.0.0 — 14 September 2026

The first stable release. Trading through OANDA and Bybit, a paper account, charts with candles, volume and footprint clusters, the trading journal, ideas as trading plans, bar replay, the economic calendar, alerts, and syncing of settings and drawings through your account.

What the number means

The third number is fixes and small work, compatible in every way. The second is new capability. The first changes when the way the thing works changes.

The sync contract is versioned separately (currently version 3) and documented in the project documentation: changing the contract means a new contract version first, and code on both sides after that.

Signing

Windows and macOS builds carry no publisher signature yet. For macOS the developer account is paid for and the signature arrives with the next release; for Windows signing is not planned for now. Details and how to verify are on the page “Why the installer is not signed”.