chore: upgrade CritterWatch to 1.0.0-beta.1 + WolverineFx to 6.16.0#117
Merged
Conversation
….3 skew
The AppHost had two Aspire version knobs out of sync: the build-time
Aspire.AppHost.Sdk at 13.3.5 and the runtime Aspire.Hosting.* packages at
13.4.3. Bump both to the current latest, 13.4.6, so they move together.
- Aspire.AppHost.Sdk 13.3.5 → 13.4.6 (CritterMart.AppHost.csproj)
- Aspire.Hosting.{AppHost,JavaScript,PostgreSQL,RabbitMQ} 13.4.3 → 13.4.6
- de-stale a Program.cs comment that named the exact patch (13.4.3)
No CritterWatch/Wolverine clash: Aspire.Hosting.* is orthogonal to the
CW↔Wolverine coupling (CW depends on WolverineFx 6.12.0, not Aspire); the only
shared axis is the .NET 10 line, which 13.4.6 stays on. The two impactful 13.4
breaking changes (Postgres default image 17.6→18.3, RabbitMQ 4.2→4.3) already
shipped with the 13.4.3 Hosting packages and are already proven — CritterMart's
Postgres is ephemeral (no WithDataVolume, no data-volume break).
Live-verified on the full Aspire stack: clean build (0 warnings), clean boot
(all three services healthy, no errors in the AppHost log), correct container
images (postgres:18.3 + rabbitmq:4.3, both crittermart-labeled), seeder ran
(crit-rare = 3), and the full Orders→RabbitMQ→Inventory cross-BC saga flow
exercised via demo-traffic.ps1 -Backorder -Cover (saga opened + resolved,
crit-rare 3→10).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
beta.1 is built against GA WolverineFx 6.16.0 (read from its nuspec), which satisfies the "revisit when a GA-Wolverine CW ships" condition (alpha.4's prerelease 6.14 line was why alpha.4 was skipped). Moving Wolverine past 6.13.x straight to 6.16.0 atomically with CritterWatch is the sanctioned coupling path and obsoletes the stranded Dependabot 6.13.x bumps. Marten 9.12.0 + JasperFx.Events 2.18.1 come transitively. MessagePack CVE (GHSA-hv8m-jj95-wg3x) still unresolved on beta.1 (transitive 2.5.302 < 3.0.214) — suppression kept, comment re-dated. - Directory.Packages.props: CritterWatch + Wolverine.CritterWatch alpha.3 → beta.1; all 8 WolverineFx.* 6.12.0 → 6.16.0; coupling + MessagePack comments rewritten. Necessitated Marten-9.12 compat fix (the bump was not zero-code): Marten 9.12 re-materializes instance-registered inline projections, dropping constructor-injected state — the two "awaiting-list" Bruun projections read their captured timeout back as default(TimeSpan), so the view's visible Deadline silently became "now". Cosmetic only (cancellation/abandonment run off the scheduled messages + the streams, not this view). Fixed by making both projections stateless fact-recorders (store PlacedAt / LastActivityAt) and computing the deadline on read in the GET endpoints (which inject the existing PaymentDeadline / CartActivityDeadline singletons). HTTP contract (responses carry Deadline) preserved. Verified: build clean (0 warnings); 149/149 tests green (the 2 bump-introduced failures fixed); full live boot on the Aspire stack — CritterWatch console up clean (no startup TypeLoadException → coupling correct) and the refactored awaiting-payment deadline reads ~7 min in the future, not "now". See docs/retrospectives/chore/004-critterwatch-next-release-upgrade.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What & why
Executes the prepared chore/004 CritterWatch upgrade. CritterWatch
1.0.0-alpha.3 → 1.0.0-beta.1, and in lockstep the Critter Stack lineWolverineFx.* 6.12.0 → 6.16.0(Marten9.12.0+ JasperFx.Events2.18.1transitive).beta.1's nuspec targets GA WolverineFx 6.16.0 (not a prerelease line) — exactly the condition for taking the upgrade (alpha.4's prerelease 6.14 line is why alpha.4 was skipped). Moving Wolverine past 6.13.x straight to 6.16.0 atomically with CritterWatch is the sanctioned coupling path and resolves the standing "DO NOT merge Wolverine 6.13.x" warning — the stranded Dependabot 6.13.x bumps are now obsolete.
The bump was not zero-code — a Marten 9.12 compat fix rides along
Marten 9.12 re-materializes instance-registered inline projections, dropping constructor-injected state. The two "awaiting-list" Bruun todo-list projections (
OrdersAwaitingPayment,CartsAwaitingActivity) read their captured timeout back asdefault(TimeSpan), so the view's visibleDeadlinesilently became "now". Impact is cosmetic only — cancellation/abandonment decisions run off the scheduled messages and the Order/Cart streams, never this view.Fix: make both projections stateless fact-recorders (store
PlacedAt/LastActivityAt) and move the deadline policy to the read side — the GET endpoints inject the existingPaymentDeadline/CartActivityDeadlinesingletons and computeDeadline = timestamp + duration. The HTTP response contract (rows carryDeadline) is preserved. This is the more idiomatic CQRS split anyway (view = facts, endpoint = policy).MessagePack CVE
GHSA-hv8m-jj95-wg3xis still unresolved on beta.1 (transitive MessagePack2.5.302< the3.0.214fix) — the<NuGetAuditSuppress>stays, comment re-verified-dated.Verification
TypeLoadException, so a healthy boot is the proof), and the refactoredGET /orders/awaiting-paymentreturned a deadline ~7 min in the future (theOrders__PaymentTimeoutknob), not "now".Supersedes
Closes superseded Dependabot PRs #104 (critter-stack group), #108 (CritterWatch alpha.4), #110 (Wolverine.CritterWatch alpha.4). (#105 aspire group is handled by #116; #106/#107/#109 are separate concerns.)
Retro:
docs/retrospectives/chore/004-critterwatch-next-release-upgrade.md.🤖 Generated with Claude Code