Bump the editor-codemirror group across 1 directory with 2 updates

[dependabot]

Bumps the editor-codemirror group with 2 updates in the / directory: @codemirror/lang-markdown and @codemirror/view.

Updates @codemirror/lang-markdown from 6.5.1 to 6.5.2

Commits

• See full diff in compare view

Updates @codemirror/view from 6.43.7 to 6.43.8

Commits

• See full diff in compare view

[ndisidore]

@dependabot rebase

[ndisidore]

@dependabot rebase

[ndisidore]

@ask-bonk review this - look for breaking changes/issues

[ask-bonk]

@ndisidore Bonk workflow failed. Check the logs for details.

View workflow run · To retry, trigger Bonk again.

[ask-bonk]

Review

This is a routine Dependabot patch-version bump within the editor-codemirror group, and I found no breaking changes or issues.

What changed:

• @codemirror/lang-markdown 6.5.1 → 6.5.2
• @codemirror/view 6.43.7 → 6.43.8
• Transitively pulled in as part of the lockfile update: @codemirror/lang-html 6.4.11 → 6.4.12 and @lezer/css 1.3.4 → 1.3.6

Assessment:

• All bumps are patch releases (semver-compatible, no API breakage expected). The ^ ranges in package.json already permitted these.
• The package.json and pnpm-lock.yaml are consistent: both direct specifiers and their pinned versions match, and @codemirror/view is propagated uniformly across every dependent snapshot entry.
• The transitive bumps (lang-html, @lezer/css) are internal to the codemirror/lezer dependency graph and are pulled in coherently by the two direct updates — not stray drift.
• Usage in packages/gatekeeper-context/app/ContextLibraryPage.tsx relies only on stable exports (EditorView, keymap, drawSelection, lineNumbers, markdown), none of which are affected by patch releases.

Note: The Bonk workflow failure noted in the prior PR comment is a CI/harness issue, not something introduced by these dependency changes.

LGTM!

github run