Repository navigation
chore: disable ex_check's usage_rules tool - #118
Merged
Merged
Conversation
ex_check 0.17.0 auto-enables a `usage_rules` tool (`mix usage_rules.sync --check`) whenever the `usage_rules` package is a dependency. This package publishes `usage-rules.md` for downstream projects but has no `usage_rules:` sync config of its own, so the check fails with "No usage_rules config found".
jimsynz
force-pushed
the
chore/disable-usage-rules-check
branch
from
October 12, 2026 02:53
c4a7f61 to
145d369
Compare
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.
ex_check 0.17.0 added a curated
usage_rulestool that runsmix usage_rules.sync --checkwhenever theusage_rulespackage is a dependency. This package publishesusage-rules.mdfor downstream consumers but doesn't sync rules from its own deps, so it has nousage_rules:project config and the check fails:Disable the tool in
.check.exs, alongside the existing{:mix_audit, false}.Also bumps
decimal3.1.1 → 3.2.0 inmix.lockto clear EEF-CVE-2026-97853 (fixed in 3.1.2), which is failingmix hex.auditonmain.