fix(caps): declare IO.Mut in Health and Metrics; 0.2.7 - #10
Merged
Merged
Conversation
0.2.6 declared IO.Mut in PubSub, IslandAssets, IslandSocket and RateLimit but missed Bastion.Health and Bastion.Metrics, which store their state in Vault the same way. Building forgepm against the published 0.2.6 on a current march therefore still fails: module `Bastion.Health` uses `IO.Mut` but does not declare `needs IO.Mut` module `Bastion.Metrics` uses `IO.Mut` but does not declare `needs IO.Mut` forge exposes no --no-cap-strict escape, so this blocks any downstream release build outright rather than merely warning. Verified by building forgepm's release binary against a patched copy: the two violations are the only ones remaining, and the build completes.
Ch4s3
force-pushed
the
claude/cap-ceiling-health-metrics
branch
from
August 13, 2026 00:40
478c804 to
5b5625f
Compare
3 tasks done
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.
0.2.6 fixed the capability ceiling for
PubSub,IslandAssets,IslandSocketandRateLimit, but missed two modules that store state in Vault the same way:So building anything downstream against the published 0.2.6 on a current march still fails.
forge buildexposes no--no-cap-strictescape (the compiler suggests the flag, forge doesn't forward it), so this is a hard block on release builds, not a warning.Found while building forgepm's production binary against published 0.2.6 — it was masked before because the previous production build used a locally-patched bastion tree.
Verified: with these two lines added, forgepm's
forge build --releasecompletes and these were the only remaining violations.Needs a publish of 0.2.7 to be useful downstream.