From 8b37e8d94ef5536db2a3fe48284540254fb7aa62 Mon Sep 17 00:00:00 2001 From: "Jeremy D. Miller" Date: Tue, 26 May 2026 20:23:57 -0500 Subject: [PATCH] Consume JasperFx 2.1.2 across all JasperFx.* packages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Bump the four JasperFx packages Marten depends on to the aligned 2.1.2 release (they now lock to a single $(JasperFxVersion) upstream): - JasperFx 2.0.1 -> 2.1.2 - JasperFx.Events 2.1.1 -> 2.1.2 - JasperFx.Events.SourceGenerator 2.1.1 -> 2.1.2 - JasperFx.SourceGenerator 2.0.1 -> 2.1.2 JasperFx.RuntimeCompiler is intentionally left alone — it versions independently upstream and is not part of the 2.1.2 set (and master no longer references it). 2.1.2 carries the #4562 event-parameter-naming generator support (accepts `ev` as a conventional event parameter name) whose docs landed in #4563. Full solution builds clean against 2.1.2 (0 errors, all 45 projects); no API adaptation needed. Co-Authored-By: Claude Opus 4.7 (1M context) --- Directory.Packages.props | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Directory.Packages.props b/Directory.Packages.props index ca6e509d2a..9d63e2b1c7 100644 --- a/Directory.Packages.props +++ b/Directory.Packages.props @@ -13,13 +13,13 @@ - - - + + + all runtime; build; native; contentfiles; analyzers; buildtransitive - +