Skip to content

Flowmark v0.6.0

Choose a tag to compare

View all tags
@Mumma6 Mumma6 released this 31 Oct 15:07
v0.6.0
32ba283
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Draft only. Do not publish until Production is verified at the main merge commit. Before publishing, change this release's target from the pre-merge candidate 32ba28359721dcfc58a97514c8295b403cbbf721 to that exact verified SHA.

Business references and outcomes

  • Find historical runs by explicitly enabled business references and categories.
  • Follow declared business outcomes over time, with totals, reason distributions, weighted ratios and the runs behind each figure. Missing reports stay unknown rather than zero or success.
  • Compare a run with an explicit earlier peer population, and distinguish repeated short operations from one long occurrence.

Runs, delivery and retries

  • The first terminal event accepted by persistence closes the run. A later conflicting terminal report returns HTTP 409 and leaves the recorded result unchanged.
  • Opt-in latest-progress delivery keeps the newest unsent progress snapshot under queue pressure. Bounded admission and local delivery health do not turn telemetry loss into a business failure.
  • Operation callbacks can report a safe error code, message and retryable flag while the application keeps its original exception.
  • Record application-owned attempt numbers and link a new execution to an earlier retry, without Flowmark deciding retry policy.

Durable expectations

  • Applications can declare expected confirmations with flow.expect(), then resolve or cancel them explicitly.
  • Deadlines are stored and evaluated on read, including after process restarts and after the run has completed. Overdue investigation is separate from execution status. Flowmark does not schedule or retry the application's work.

Compact historical facts

  • Run summaries, search, outcome windows, technical metrics and operation comparison can read compact facts maintained in the same transaction as each accepted event.
  • Migrations 0015 and 0016 install that projection without scanning existing history. Unbackfilled runs still read raw events. Hosted backfill is a separate operation and is not part of this release.
  • Migrations 0011–0014 add search configuration, attempt metadata and expectation storage. They are additive. Rolling the application back does not undo the schema.
Assets 2
Loading