Skip to content

0.7.1

Choose a tag to compare

View all tags
@jeremydmiller jeremydmiller released this 15 Aug 16:55
· 11 commits to main since this release
v0.7.1
f48b25b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A dependency bump, with one piece of code coming back out.

JasperFx 2.48.0

All four JasperFx packages move together. Fisher 0.7.1 requires JasperFx 2.48.0 — see below for why that is a real floor rather than a preference. Weasel stays at 9.24.0, which is still current.

2.48.0 adds no compliance suite and changes no existing suite file, checked by diffing the package contents rather than assumed. All 32 suites and 272 tests remain enrolled and green, with enrollment re-verified by extracting the package's *Compliance classes and diffing against the enrolled list.

The fisher#72 workaround is removed

jasperfx#663 shipped in 2.48.0. That is the upstream half of the #72 fix released in 0.7.0: StreamAction.Append(graph, string, …) appended straight to the backing list where the Guid overload beside it went through AddEvent, so every event appended to a string-identified stream reached an inline projection with an empty StreamKey. Upstream now routes both string overloads through AddEvents.

Fisher had been stamping the identity in its own append planner. That workaround is gone, following the standing rule that a workaround is filed upstream and taken back out when the fix ships — the same cycle FisherCommandBuilder completed for weasel#424.

Nothing about the behaviour changes. It was verified by deleting the stamping and running the full suite against 2.48.0, including the test written to fail without it; that test now guards the upstream fix rather than a Fisher workaround, and still pins both the string and Guid halves so a later release cannot silently change which one is covered.

This removal is what makes 2.48.0 a hard floor: on an older JasperFx, IEvent.StreamKey would be blank inside an inline projection again. NuGet enforces it.

The bundled source generator moves with it

Fisher has carried JasperFx.Events.SourceGenerator inside its own package since 0.7.0, so 2.48.0's batch of source-generator fixes now reaches consumers through Fisher. One of them changes the generator to report unregistered published types instead of skipping them in silence; it emits nothing against Fisher itself, confirmed by diffing full-build warning counts code for code against 2.47.0.

Verified

Release build, all three suites, both target frameworks: 1228 + 36 + 13, zero failures on each.

Full changelog: v0.7.0...v0.7.1

Assets 2
Loading