Skip to content

fly: adopt mudflaps 0.4.0 (roadmap cleared: signal/exec/ps)#820

Merged
lex00 merged 1 commit into
mainfrom
feat/adopt-mudflaps-0.4.0
Jul 12, 2026
Merged

fly: adopt mudflaps 0.4.0 (roadmap cleared: signal/exec/ps)#820
lex00 merged 1 commit into
mainfrom
feat/adopt-mudflaps-0.4.0

Conversation

@lex00

@lex00 lex00 commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Follows the mudflaps v0.4.0 release (INTENTIUS/mudflaps#57), which implements the last three Machines roadmap endpoints (signal/exec/ps) and clears the mudflaps roadmap.

What

Bump the single-source MUDFLAPS_IMAGE pin 0.3.10.4.0.

flyApply doesn't call the new endpoints, so behavior is unchanged — this adopts the release deliberately (rather than waiting for the weekly freshness notice) and keeps the pin current.

Validation (live against ghcr.io/intentius/mudflaps:0.4.0)

  • machines-contract docker coverage test — contract ⊆ implemented, no roadmap dependency (roadmap now empty).
  • fly-apply docker integration test — flyApply's full apply/rollback loop against 0.4.0.
  • Full fly suite green (27 files); emulator-freshness now reports both emulators current (mudflaps 0.4.0, spritzer 0.3.1).

No other changes needed

  • MACHINES_CONTRACT unchanged — signal/exec/ps aren't part of the applier's surface.
  • No tutorial / lexicon-doc updates — chant's mudflaps references are all generic ("the flaps fake"), never version- or roadmap-specific.
  • spritzer has no roadmap (its health emits no unimplemented list), so nothing to release there.

mudflaps 0.4.0 implements the last three Machines roadmap endpoints
(signal/exec/ps) and clears its roadmap. Bump the single-source pin from 0.3.1.

flyApply doesn't call the new endpoints, so behavior is unchanged — this adopts
the release we cut deliberately and keeps the emulator-freshness check quiet.
Verified live against ghcr.io/intentius/mudflaps:0.4.0: the machines-contract
coverage test (contract ⊆ implemented, no roadmap dependency) and the flyApply
integration test both pass; the freshness check now reports mudflaps current.

The MACHINES_CONTRACT is unchanged — the new endpoints aren't part of the
applier's surface. No tutorial or lexicon-doc changes needed: chant's mudflaps
references are generic ("the flaps fake"), never version- or roadmap-specific.
@lex00
lex00 merged commit 7943ad6 into main Jul 12, 2026
5 checks passed
@lex00
lex00 deleted the feat/adopt-mudflaps-0.4.0 branch July 12, 2026 17:31
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