Skip to content

Commit e142f12

Browse files
committed
docs(deps): state what check-override-consistency measurably says about the katex entry
The note claimed the gate lists katex as an override it cannot cross-check. Measured on this tree, it says nothing about the entry: nothing publishable declares katex, mermaid consumes it, and the selector's bound clears the target floor, so neither census reports it. Claude-Session: https://claude.ai/code/session_01VF48aw8RPG6wzDnMgp6rtw Co-authored-by: Claude <noreply@anthropic.com>
1 parent 9307314 commit e142f12

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

‎pnpm-workspace.yaml‎

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -560,10 +560,12 @@ overrides:
560560
# The target resolves to 0.18.10, not 0.18.11: 0.18.11 is deprecated on
561561
# npm ("Accidentally published with breaking changes"), and pnpm skips it.
562562
# Transitive-only and docs-only: nothing publishable declares katex, so
563-
# check-override-consistency.mjs lists it as an override it cannot
564-
# cross-check against a declared range — correct for this shape. The
565-
# floor is the advisory's 0.11.0; the bound is 0.19.0, the caret boundary
566-
# of the 0.18 target line, per this block's header rule — never `<0.18.2`.
563+
# check-override-consistency.mjs's manifest rule has no declared range to
564+
# hold in lockstep and says nothing about this entry (measured; neither
565+
# census lists it: mermaid consumes it, and the bound clears the target
566+
# floor). The floor is the advisory's 0.11.0; the bound is 0.19.0, the
567+
# caret boundary of the 0.18 target line, per this block's header rule —
568+
# never `<0.18.2`.
567569
# Re-check when a mermaid release declares a katex range that admits
568570
# 0.18.2: the entry then turns into a dedupe and stays as the floor.
569571
'katex@>=0.11.0 <0.19.0': '^0.18.2'

0 commit comments

Comments
 (0)