Skip to main content

Core Release Plan

Planning related to the evolution of the central infrastructure, the low-code engine, queue and buffer management, security, and the user interface.

Releases are organized by version number and planned period (week or month).

Core history

For the history of already published releases, see the Changelog.

Release 1.9.10​

Planned for: week of 21–27 September 2026

Added​

  • Payload modification marker to distinguish a replace from an upsert of mutable fields.
  • New two-step archival algorithm.

Changed​

  • Improved persistence of queue dates.
  • Optimized message status change.

Release 1.10.0​

Planned for: October 2026

Refactor and fixes​

  • Code optimization and cleanup.
  • PWA enablement for reload after a release, with cache cleanup.
  • New hourly statistics snapshotting method, currently under verification. UI connection will follow later.
  • Documentation of message and batch status.
  • Edge-case analysis on inconsistent data (in progress).
  • Deletion.
  • Heartbeat to Hyperping for services that are not exposed.
  • Beta features per tenant.
  • Optimized hourly statistics refresh.
  • Sources and destinations with multipart/form-data support.
  • Fix for key casing on messages ingested from MySQL.
  • Removal of Sum and Count from aggregator types.

Frontend​

  • Frontend conversion to TypeScript.
  • Adoption of services and code reuse.
  • Error display contextual to the flow.

Low code​

  • Ability to create reusable libraries.
  • Ability to test data sources through a sandbox, with data displayed in a table.

App Marketplace​

  • External sources.
  • Flow structure revised to support future evolutions (v2).
  • Per-tenant marketplace, with the ability to upload custom adapters and reusable actions.

AI​

  • Magic wand for low code: given input and output, it generates C# code.
  • Error diagnostics: analyzes the error and suggests recommendations.