fix(docs): re-pin @mermaid-js/layout-elk to ^0.1.9 (un-red dev docs build)#435
Merged
Merged
Conversation
…id peer) Dependabot #429 (9039805) bumped @mermaid-js/layout-elk ^0.1.9 → ^0.2.2, re-introducing the exact peer-dependency conflict that #391 had previously pinned away: @docusaurus/theme-mermaid@3.10.2 requires @mermaid-js/layout-elk @^0.1.9, so `make docs-install` (`npm install`) fails with ERESOLVE. This reds the Deploy-Documentation `build` job (a required check), blocking every PR whose test-merge inherits dev's package.json. Re-pins to ^0.1.9 and regenerates the lockfile (layout-elk resolves 0.1.9). `cd docs && npm install` now exits 0. Mirrors #391. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sunholo-voight-kampff
enabled auto-merge (squash)
July 20, 2026 13:49
|
sunholo-voight-kampff
added a commit
that referenced
this pull request
Jul 21, 2026
…sumed orphaned crashed run) (#436) Resumed the orphaned crashed iter-70: PR #434 held a complete, evaluated inline-interior inner loop (executor opus M0-M3, evaluator sonnet PASS 91/100 r1) killed by an 18h reboot outage pre-Gate-3b/4. Diagnosed the sole red (docs-build) as a stale-base mermaid npm ERESOLVE (branch cut before #435 re-pin), fixed via gh pr update-branch → CI green → auto-merge squashed 3c1cec5. - queue tag: m-ailang-fmt-inline-interior PARKED iter-67 → LANDED iter-70 - STATUS: +iter-70 stamp, iter-63 rotated to archive - log entry #75 fmt polish pair now fully LANDED; next non-parked pick = m-eval-fmt-weakmodel-ab. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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.
Problem
Dependabot #429 (
9039805e4) bumped@mermaid-js/layout-elk^0.1.9→^0.2.2, re-introducing the peer-dependency conflict that #391 had previously pinned away.@docusaurus/theme-mermaid@3.10.2declarespeerOptional @mermaid-js/layout-elk@^0.1.9, somake docs-install(npm install) fails:This reds the Deploy Documentation
buildjob — a required status check (test/lint/build) — so it blocks every open PR whose test-merge inherits dev'spackage.json(observed on #434).Fix
Re-pin to
^0.1.9(matching the peer) and regenerate the lockfile — mirrors the prior fix #391. Verified locally:cd docs && npm installexits 0, lockfile resolveslayout-elk@0.1.9.Why not just bump theme-mermaid
theme-mermaid is pinned at
3.10.2(the whole docusaurus group), and0.2.xof layout-elk isn't in its peer range. Re-pinning layout-elk is the minimal, proven fix. A future coordinated docusaurus-group bump can lift both together.Found + fixed during mission-control iteration 70 (un-red dev is the mission's job).
🤖 Generated with Claude Code