Release v22.6.0

Summary

Records which command is executing on the causation chain, so every event a command appends carries the command that produced it — and, when one command executes another, the command one level up. Also brings every dependency to its latest version, including Cratis.Chronicle 16.39.1.

Added

• Events appended by a command now carry a Command causation naming that command. The chain already said how the work arrived — an HTTP request, a reactor — but not what was asked for, so an appended event could be traced back to a request path and no further. A command executed from another command stacks its link on the outer one's, which is what makes "the command one level up" answerable.

Changed

• Every dependency updated to its latest version, including Cratis.Chronicle 16.39.1 and the Cratis.Fundamentals 7.18.2 / Cratis.Metrics.Roslyn 7.18.2 it requires.

Fixed

• The Chronicle Published automation retried a version conflict for ten minutes and then reported it as a NuGet indexing timeout. A conflict is a decision the workflow cannot make — the new Chronicle wants a dependency newer than the version pinned here — so it now fails immediately with the conflicting pins instead of blaming NuGet. This is what made the 16.39.1 update fail.
• The same automation merged its update with --squash, which collapses the branch's commits into a new one and leaves the originals unreachable. It now merges with a real merge commit.