Skip to content

tidy: packages — Critter Stack refresh (WolverineFx 6.8 → 6.17)#41

Merged
erikshafer merged 2 commits into
mainfrom
tidy/critter-stack-package-refresh
Jul 10, 2026
Merged

tidy: packages — Critter Stack refresh (WolverineFx 6.8 → 6.17)#41
erikshafer merged 2 commits into
mainfrom
tidy/critter-stack-package-refresh

Conversation

@erikshafer

Copy link
Copy Markdown
Owner

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:

Package Before After
WolverineFx.* 6.8.0 6.17.0
Marten (transitive) 9.14.0
JasperFx (transitive) 2.24.1
Weasel (transitive) 9.16.2
Alba 8.5.2 8.5.2 (already latest)

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

  • Restore: green — resolved WolverineFx 6.17.0 + Marten 9.14.0 cleanly.
  • Build: dotnet build CritterCab.slnx0 errors, 0 code changes needed. Clean drop-in.
  • Tests: deferred to CI. The local run was blocked by a degraded Docker Desktop engine (Testcontainers container start hangs 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

  • Pre-existing NU1903 warning (Microsoft.OpenApi 2.0.0) is unrelated to this bump.
  • Retro to be appended once CI confirms the test result.

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.
@erikshafer erikshafer self-assigned this Jul 10, 2026
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
erikshafer merged commit 01dc8bb into main Jul 10, 2026
1 check passed
@erikshafer
erikshafer deleted the tidy/critter-stack-package-refresh branch July 10, 2026 18:43
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant