Skip to content
Fexl Lite

Release notes

Per-version changelog for Fexl Lite. Each page lists the user-visible changes with <ChangeBadge> pills (feature / perf / fix / breaking), inline <BugFixBadge> references back to the original bug numbers, and any database migrations that ran on first boot.

Updated 9 May 2026·Current v1.6.105

Channels

  • Staging — fexl-v{version}-staging-windows. Each tag also has a Mac and Linux companion (Tauri builds + Docker server + web deploy).
  • Stable — fexl-v{version}-windows. Same shape, fewer tags. Promoted from staging after a QA pass.

The current shipping build is retail-server-v1.6.105 and retail-web-v1.6.105.

Versions

LATEST

v1.6.105 — partial-paid return debt-deduction + stale-productId repair

Customer-reported return-balance bug closed. Migration v96 repairs stale productIds left behind by an earlier sync-pull regression. Snapshot restore now replays gap migrations. Plus permission-gate hardening and Dashboard / Invoices revenue parity.

 MAJOR

v1.6.100 — FIFO foundations + return-wizard rebuild

The biggest single release. Per-layer FIFO replaces weighted-average; the return wizard is rebuilt around it; 25+ retest fixes ship across POS, inventory, returns, reports, shipping, settings, and expenses. 7 database migrations.

 PATCH

v1.6.99 — Postgres timestamptz round-trip

A one-fix patch landing two days before v1.6.100. ToString now formats time.Time values as RFC3339 so PG timestamptz columns round-trip cleanly. Cloud-only impact.

 PATCH

v1.6.98 — Postgres JE column gap

Migration 006 adds je.source_type / source_id / source_uuid + jel.account_code that the cloud schema had been missing. Backfills account_code on historical lines. Cloud-only impact.

How to read these pages

Each release-notes page leads with the marquee item — the change most likely to affect how you operate. Below that, fixes are grouped by domain (POS / Inventory / Returns / Reports / Shipping / Settings / Expenses), then a Database migrations table, then an Upgrading section.

Inside the body:

  • <ChangeBadge tag="feature" /> — net-new functionality
  • <ChangeBadge tag="perf" /> — performance or migration work
  • <ChangeBadge tag="fix" /> — defect repair
  • <ChangeBadge tag="breaking" /> — schema or behavioural change you should know about before upgrading

Inline <BugFixBadge bug={N} version="..." /> chips link the entry back to the original bug number, and forward to whichever doc page deep-dives the affected flow.

Upgrading

Desktop tenants auto-update on next launch via the Tauri updater. Cloud tenants pick up the new build on the next deploy. Migrations run on first boot of the new binary; they’re idempotent (safe to re-run) and they finish in seconds for typical stores, longer on large ledgers.

There’s no manual step. Reports recompute the next time they’re opened — that’s normal post-upgrade behaviour, not a regression.