tidy: packages — Critter Stack refresh (WolverineFx 6.8 → 6.17)#41
Merged
Conversation
Bump the WolverineFx family 6.8.0 → 6.17.0 (all nine pinned entries). Only the WolverineFx.* packages are pinned in CPM; Marten, JasperFx, and Weasel flow transitively and resolve to the aligned 6.17 line (Marten 9.14.0, JasperFx 2.24.1, Weasel 9.16.2). Alba is already at latest (8.5.2), unchanged. Minor bump within the 6.x line (the 5→6 / Marten 8→9 migration is already behind us): clean drop-in — restore + `dotnet build CritterCab.slnx` green with zero code changes. Discharges the "full-suite 6.x refresh still owed" item tracked since the Grpc/Polecat island was closed to 6.8 (PR #35). Local test run blocked by a degraded Docker Desktop engine (Testcontainers container start hangs before any app code runs) — deferring the test gate to CI, which exercises the suite in a clean Linux Docker environment.
Records the WolverineFx 6.8 → 6.17 bump, the build + CI 11/11 verification, and the local-Docker caveat. Indexed in the retrospectives README.
erikshafer
added a commit
that referenced
this pull request
Jul 10, 2026
…nsport build Introduces three handoff notes tracking Telemetry chain progression from PR #39 (protos) through PR #42 (skeleton + slice 1). Post-PR-42 handoff orients next session on PR B: slices 4+2 paired (LastKnownPosition store + ReportLocations gRPC ingest), CritterCab's first gRPC surface in code and first Kafka testcontainer. Documents verified WolverineFx.Grpc client-streaming gap (must hand-wire against IMessageBus through 5.37.2; 6.17 unconfirmed), local Docker wedged state (lean on CI), and ADR-011 amendment locked (IInitialData bootstrap + last-writer-wins singletons). Supersedes three earlier untracked handoffs after PR #40 (narrative decision—does not apply, recorded) and PR #41 (package refresh to 6.17.0) both merged. Carries forward design-locked guardrails, three W006 §11 ADR candidates, and open skill-debt items. Includes narrative-decision and post-PR-41 intermediate handoffs for session lineage; all disposable once next session orients.
1 task
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
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
Bumps the WolverineFx family 6.8.0 → 6.17.0 (all nine pinned entries in
Directory.Packages.props). Only the WolverineFx.* packages are pinned under Central Package Management; Marten, JasperFx, and Weasel flow transitively and resolve to the aligned 6.17 line:Why
Discharges the "full-suite 6.x refresh still owed" item tracked since the Grpc/Polecat version island was closed to 6.8 (PR #35). This is a minor bump within the 6.x line — the hard 5→6 / Marten 8→9 migration is already behind us.
Verification
dotnet build CritterCab.slnx— 0 errors, 0 code changes needed. Clean drop-in.starthangs before any Wolverine/Marten code runs — ruled out as bump-related three ways). CI exercises the full suite in a clean Linux Docker environment — this PR's CI run is the test gate.Notes
NU1903warning (Microsoft.OpenApi 2.0.0) is unrelated to this bump.