build(deps): bump @codemirror/view from 6.34.1 to 6.39.15 in /console

[dependabot]

Bumps @codemirror/view from 6.34.1 to 6.39.15.

Changelog

Sourced from @​codemirror/view's changelog.

6.39.15 (2026-02-20)

Bug fixes

Fix a regression where the editor would forget previously measured line heights without good reason.

Fix an issue where scrolling the cursor into view sometimes wouldn't work on Chrome Android.

Fix a bug that broke composition inside of block wrappers.

6.39.14 (2026-02-12)

Bug fixes

Improve performance of posAtCoords on long lines.

Fix a regression where copy and cut in a shadow DOM on Safari would fall back to the native behavior, often copying the wrong text.

6.39.13 (2026-02-08)

Bug fixes

Fix an issue where a widget at start or end of line, when wrapped to cover that whole line, could block vertical cursor motion.

Fix an issue EditorView.moveVertically that would sometimes cause selection-extending vertical motion to get stuck on line wrapping points.

6.39.12 (2026-01-30)

Bug fixes

Fix a bug where the visual selection drawn by drawSelection could fail to update properly in some circumstances.

Fix a bug where PageUp/PageDown near the edge of the viewport might completely skip to the start/end of the document.

Fix a regression that caused mark decorations to be split on text node chunk boundaries again.

6.39.11 (2026-01-14)

Bug fixes

Avoid handling copy events for parent editors.

6.39.10 (2026-01-13)

Bug fixes

Fix a regression in the way widget are reused when content next to them changes.

Make sure font metrics get recomputed on fonts.ready even if the line height doesn't change.

... (truncated)

Commits

• 218358b Mark version 6.39.15
• f8458ad Fix a bug that broke composition inside of block wrappers
• e7ca47d Add a kludge to scroll things into view in the presence of a mobile virtual v...
• f619d7f Avoid unnecessary height refreshes
• 9b8a0bd Mark version 6.39.14
• 754829b Fix a regression in copy/cut on Safari in shadow DOM
• d2c38fb Try to tweak test to run on CI
• a308203 Rewrite posAtCoords algorithm for inline content
• b3362d2 Add some more coordsAtPos tests
• 6a93b6f Mark version 6.39.13
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Thanks for opening this PR! Here are a few tips to help make the review process smooth for everyone.

PR title guidelines

• Use imperative mood: "Fix X" not "Fixed X" or "Fixes X"
• Be specific: "Fix panic in catalog sync when controller restarts" not "Fix bug" or "Update catalog code"
• Prefix with area if helpful: compute: , storage: , adapter: , sql:

Pre-merge checklist

• The PR title is descriptive and will make sense in the git log.
• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).