[Simon-He95]

Summary

• Bump markstream-vue from 2.0.11 to 2.0.24 (latest stable).
• Refresh the lockfile for its coordinated transitives: markstream-core 2.0.24, stream-markdown-parser 1.2.25, markdown-it-ts 1.1.3, and @chenglou/pretext 0.0.9.

Why

2.0.24 brings the accumulated parser, streaming, and rendering fixes since 2.0.11, including:

• streaming text fade/final rendering alignment across renderers
• parser fixes for comparison text (a<b && c>d), footnotes, CJK emphasis, and list/thematic-rule boundaries
• Mermaid/D2/Infographic preview sizing and panning fixes
• streaming performance improvements (sync layout work, height estimation, node reuse)

No breaking API changes for our integration: NodeRenderer, CodeBlockNode, PreCodeNode, MermaidBlockNode, setCustomComponents, normalizeLanguageIdentifier, getLanguageIcon, the worker entry points, and setStreamDiffsWorkerPool are all unchanged. The peer dependency ranges remain compatible with our installed versions.

Verification

• pnpm install --frozen-lockfile
• pnpm run format:check
• pnpm run lint
• pnpm run i18n
• pnpm run typecheck:web and pnpm run typecheck:node
• pnpm run test:renderer — 287/288 files and 2756/2757 tests passed; one unrelated ChatStatusBar test hit the 10s timeout under full-suite load and passed on isolated rerun (92/92).

No UI changes, so no before/after layout is needed.

Summary by CodeRabbit

• Chores
  • Updated supporting software. No user-facing changes are included in this update.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The markstream-vue development dependency version in package.json changes from 2.0.11 to 2.0.24.

Changes: Development Dependency Update

Layer / File(s)	Summary
Update markstream-vue version package.json	The declared development dependency version changes from 2.0.11 to 2.0.24.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: zerob13

Merge Risk: Minimal · up to 5a28e

The dependency and lockfile versions are aligned, with no unresolved merge-blocking issue identified.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title "chore(deps): upgrade markstream-vue to 2.0.24" matches the only functional change in the changeset. The diff bumps the markstream-vue dev dependency from 2.0.11 to 2.0.24 in package.json. T…
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title "chore(deps): upgrade markstream-vue to 2.0.24" matches the only functional change in the changeset. The diff bumps the markstream-vue dev dependency from 2.0.11 to 2.0.24 in package.json. The PR objectives confirm the same upgrade and the refreshed lockfile. The title is specific and follows a conventional commit style.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 36115bc6-3663-4816-8598-f358999f4f55

Commits

Reviewing files that changed from the base of the PR and between 3db91f8 and 5a28efb.

Files ignored due to path filters: 1

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

Files selected for processing: 1

• package.json

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

[zerob13]

Review: approved

This is a scoped dependency upgrade: markstream-vue 2.0.11 → 2.0.24, plus the four packages it owns in the lockfile (markstream-core, stream-markdown-parser, markdown-it-ts, @chenglou/pretext). Nothing else in the repo changes.

I verified the published packages, not just the diff:

• The package export map is identical between 2.0.11 and 2.0.24. Both worker entries (katexRenderer.worker, mermaidParser.worker) and all three stylesheet entries still exist, so every import path DeepChat uses remains valid.
• The NodeRenderer prop surface is unchanged. The type additions are additive only (clipboardWriter, fitPreviewHeight, estimatedPreviewHeightPx, markup, optional maxChars on flush), so no call site needs updating.
• CSS class names and --ms-* custom properties used by DeepChat are unchanged. Only Vue scoped-style hashes differ, which is expected from a rebuild.
• 2.0.24 is the current latest tag on npm.
• pnpm install --frozen-lockfile resolves cleanly, so package.json and the lockfile agree.

Local verification at 5a28efb:

• pnpm run typecheck:web passes.
• 8 relevant renderer suites pass (108 tests): MarkstreamDomContract, MarkdownRenderer, ThinkContent, MessageBlockToolCall, markdownWorkerLifecycle, markstreamTailwindSource, AboutUsSettings, ReleaseNotes.
• No new tests were added, which is correct for a dependency-only change.

Residual risk: this component renders every chat message and code block, so jumping 13 patch releases does touch core UI behavior (streaming, parsing, Mermaid/D2 previews). The automated tests cover the DOM contract but not the visual result. CI build and static already pass; test-main, test-renderer, and packaging are still running. Approval should not be read as replacing those checks.

No blocking findings.