fix(docs): pin @mermaid-js/layout-elk to ^0.1.9 (fixes flaky docs build)#391
Merged
Conversation
…d peer The docusaurus group bump (#373) moved @mermaid-js/layout-elk to ^0.2.2, but @docusaurus/theme-mermaid@3.10.2 declares peerOptional @mermaid-js/layout-elk@^0.1.9. Since docs-install runs `npm install` (not `npm ci`), the ERESOLVE peer conflict surfaced intermittently and made the required `build` check flaky (#373's own run shows both a pass and a fail; #390 hit it too). theme-mermaid is locked to the docusaurus 3.10.x line, so it can't move to a layout-elk 0.2.x peer without a full docusaurus major upgrade. Pin layout-elk back to ^0.1.9 (0.1.9 is the version dev ran before #373) so npm install resolves deterministically. Regenerated package-lock.json. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sunholo-voight-kampff
enabled auto-merge (squash)
July 14, 2026 10:15
sunholo-voight-kampff
added a commit
that referenced
this pull request
Jul 20, 2026
…id peer) (#435) 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>
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
The
buildCI check has been flaky since the docusaurus group bump #373. That PR moved@mermaid-js/layout-elkto^0.2.2, but@docusaurus/theme-mermaid@3.10.2declares:make docs-installrunsnpm install(notnpm ci), which re-resolves peers on every run, so the conflict surfaces as an intermittentERESOLVEfailure. Evidence it's flaky, not hard-broken: #373's own commit has both a passing and a failingbuildcheck-run, and #390 failed then passed on retry.Left unfixed, this randomly reds-out every PR's required
buildcheck and can stall the new Dependabot auto-merge (it waits for green).Fix
@docusaurus/theme-mermaidis pinned to the docusaurus 3.10.x line, so it can't adopt a layout-elk 0.2.x peer without a full docusaurus major upgrade. Pinlayout-elkback to^0.1.9— the version dev ran before #373 — sonpm installresolves deterministically. Lockfile regenerated;npm installverified clean (no ERESOLVE), 0 remaining 0.2.2 refs.🤖 Generated with Claude Code