VisualHFT Docs Changelog Research
Release ledger

Changelog

A public, sanitized ledger of released VisualHFT product builds. These entries cite private product-release tags; the open-source repository keeps a separate project-history changelog.

Open-source project history ↗ Installation guide
Stable Latest

v0.1.11

Encrypted plugin delivery on clean installations

The stable release that completed the plugin-delivery path and proved encrypted plugins on a clean Windows installation.

VisualHFT v0.1.11 delivery path from release package and encrypted plugin through verification, dependency checks, and plugin load
Released plugins are delivered, verified, discovered, entitled, and loaded through the product path—not copied from developer output.

This release completes the production plugin-delivery correction introduced after clean-machine testing exposed a difference between developer output and the installed application.

The acceptance run used an isolated Windows environment, the release-shaped installer, and a real encrypted plugin package. The result established that encrypted delivery, discovery, entitlement, and loading complete on a machine without a developer workspace.

Operator impact

Users receiving an entitled plugin through the released catalog no longer need a plaintext development copy for the plugin to load. Upgrade from earlier 0.1.x builds when using delivered plugin packages.

Highlights

  • Encrypted plugins now load on a clean installation.
  • The release was validated against the production-shaped installer and plugin catalog.
  • Plugin discovery accounted for all packaged entries with no load failures in the acceptance run.
Source: v0.1.11
private github release
Stable

v0.1.8

Plugin dependency isolation on installed builds

A stable release constraining plugin dependency maps to declared, verified dependencies after clean-machine testing exposed an application-load-context failure.

VisualHFT v0.1.8 plugin dependency map changing from installed-directory sweeping to declared SHA-256-verified dependencies
Each plugin now resolves only the dependencies declared for its package instead of inheriting the installed application directory.

Clean-machine testing found that an installed plugin could build its private dependency map from the entire application directory. That allowed framework and WPF assemblies to enter the plugin load context and fail during UI resource resolution.

The loader now constructs the map from declared dependencies only, verifies those dependencies, and leaves the map empty when a package declares none. A plugin that has already loaded into memory also no longer falls back to a plaintext twin after a later encrypted-package failure.

Operator impact

This release is an intermediate repair in the plugin-delivery sequence. Use v0.1.11 or newer for the complete clean-install encrypted-plugin acceptance path.

Highlights

  • Stopped plugin load contexts from sweeping every assembly beside the installed application.
  • Scoped dependency loading to declared, SHA-256-verified dependencies.
  • Added a release-shaped solution build gate and documented the customer-fidelity test boundary.
Source: v0.1.8
private github release
Stable

v0.1.4

GPU stability and replay trigger evaluation

A stable release correcting GPU chart context lifetime and preventing stale trigger observations from refiring during replay.

VisualHFT v0.1.4 correction of GPU graphics-context lifetime and stale replay trigger evaluation
The release corrected two separate boundaries: GPU chart context ownership and replay trigger consumption.

This release stabilizes the GPU rendering path by correcting the ownership and lifetime of the graphics context used by chart surfaces. It also prevents an already-consumed observation from being evaluated again as replay state advances.

Operator impact

Upgrade if you use GPU-enabled charts or depend on trigger rules during replay. The changes affect stability and trigger evaluation; they do not change market-data formats.

Highlights

  • Corrected a GPU zero-copy rendering crash caused by graphics-context lifetime.
  • Prevented stale Trigger Engine observations from refiring during replay.
  • Validated focused GPU, trigger, event-capture, and replay-routing suites.
Source: v0.1.4
private github release
Stable

v0.1.1

Stable channel identity correction

The first production-stable 0.1 release, correcting channel-aware desktop release identity during startup.

VisualHFT v0.1.1 stable installer channel resolving to the corrected stable startup identity
The stable installer and startup identity now agree; v0.1.0 remains superseded.

This release supersedes the original v0.1.0 stable candidate. The application now recognizes its stable-channel identity instead of applying the beta-only identity guard during startup.

Operator impact

Do not use v0.1.0. Install v0.1.1 or a newer stable version.

Highlights

  • Made desktop release identity aware of stable and beta channels.
  • Corrected a startup failure in the original stable candidate.
  • Revalidated the production installer on an isolated Windows environment.
Source: v0.1.1
private github release