Skip to content

Changelog

This page tracks notable changes in paid LiMon product builds.

  • Standard release notes are included here
  • Professional release notes are included here
  • Community users can inspect public source history directly in the public Git repository: LiMon core on GitHub

The entries below summarize the most important user-facing additions, platform improvements, and upgrade-relevant fixes across recent paid releases.

2026.1

Edition scope: Standard and Professional

Highlights

  • Matured the native-package release line with paid .deb and .rpm artifacts, deterministic package validation, and stronger install/bootstrap behavior.
  • Improved offline install readiness by bundling Python dependencies per supported interpreter path and tightening the packaged limon-setup bootstrap flow.
  • Expanded historical-data capabilities with multi-vendor log import for FlexLM, RLM, and LM-X, using a unified parser-selection path.
  • Added Chargeback as a web-first intelligence report with export support instead of treating it as another PDF-only workflow.

Fixes

  • Fixed several native-package edge cases around bundled Python dependencies, package metadata, and first-run bootstrap recovery.
  • Corrected package acceptance issues in both DEB and RPM validation lanes.
  • Improved release artifacts so paid Docker and package outputs contain the expected files without duplicate or misleading payloads.

Upgrade Notes

  • No data migration is expected.
  • If you automate .deb or .rpm installs, review the current package-install flow and supported Python/runtime expectations before upgrading.

2025.3

Edition scope: Standard and Professional

Highlights

  • Added live intelligence report pages and report services so key report flows can be explored in the web UI, not only as generated files.
  • Added a live Compliance Ledger panel and folded compliance context more deeply into the Audit Defense experience.
  • Expanded Savings report scenario analysis so teams can compare both seat-count and pricing assumptions from the report UI.
  • Added report scheduling and report settings support to the paid administration workflow.

Fixes

  • Improved timezone handling and surfaced site timezone context more clearly in site cards and details.
  • Refined report behavior for applications without cost data so capacity analysis still remains usable.
  • Improved report rendering and export behavior across intelligence views.

Upgrade Notes

  • Review report settings after upgrade if your team relies on scheduled or customer-facing intelligence outputs.

2025.2

Edition scope: Standard and Professional

Highlights

  • Added first-class native package installation with the limon-setup wrapper and a guided packaged setup path.
  • Reworked paid Docker delivery around offline-friendly bundles and docker-install.sh so commercial installs no longer depend on a live registry pull.
  • Added limon-diag support-bundle tooling to make customer troubleshooting faster and more consistent.
  • Strengthened end-to-end release validation so Docker and packaged builds are exercised before publication.

Fixes

  • Fixed setup and packaging edge cases across paid Docker distribution and packaged install paths.
  • Improved deployment route handling so /admin/ and /setup/ work consistently on supported deployment routes.
  • Corrected early release-process issues in offline bundle assembly and validation.

Upgrade Notes

  • If you are upgrading from older commercial builds, align your operational runbooks with limon-setup, limon-diag, and the offline Docker bundle flow.

2025.1.2

Edition scope: Standard and Professional

Highlights

  • Refreshed the paid frontend with a stronger dashboard shell, better header behavior, and cleaner intelligence entry points.
  • Added report configuration controls to the Admin UI so teams can manage presentation details of paid intelligence outputs.
  • Added clearer license and subscription-renewal entry points inside the product UI to reduce friction around commercial lifecycle tasks.

Fixes

  • Fixed dynamic-name rendering issues in the frontend and improved internationalized UI behavior.
  • Clarified toolbar actions and several day-to-day admin interactions.
  • Improved theme consistency and overall paid UI polish.

Upgrade Notes

  • No special migration is expected, but teams using generated reports should review the new Admin report settings after upgrade.

2025.1

Edition scope: Standard and Professional

Highlights

  • Expanded the commercial platform with a clearer 60-day Professional evaluation flow.
  • Added subscription-status visibility in the product header and improved commercial lifecycle messaging in the paid UI.
  • Continued the frontend modernization with a stronger dashboard experience and cleaner paid-platform navigation.

Fixes

  • Improved paid-edition copy and UX around setup, licensing, and subscription state.
  • Refined theme consistency and reduced UI friction in common first-run workflows.
  • Improved documentation and product guidance for the commercial platform.

Upgrade Notes

  • Customer-facing copy now prefers evaluation over trial, although some internal technical contracts still retain trial naming.

2024.3

Edition scope: Standard and Professional

Highlights

  • Established the first commercial release line for LiMon.
  • Introduced the Setup Wizard, Admin UI, and paid-platform operational workflow around DB-backed configuration.
  • Added the first intelligence-reporting capabilities, including Savings Report and Audit Defense outputs for subscribed paid customers.
  • Added commercial licensing and platform-tier gating for Standard and Professional deployments.
  • Shipped native Linux package and Docker deployment options for self-hosted installs.

Fixes

  • Improved first-run setup validation for database connectivity, binary paths, and server reachability.
  • Corrected early setup-order issues so installation and configuration steps occur in the right order.

Upgrade Notes

  • Customers moving from Community to a paid platform can keep the same core deployment model and data footprint while switching to the paid setup and activation flow.