Skip to content

chore(deps): bump marked from 15.0.12 to 17.0.6#2012

Draft
martin-helmich wants to merge 1 commit into
masterfrom
worktree-salvage-marked-1770
Draft

chore(deps): bump marked from 15.0.12 to 17.0.6#2012
martin-helmich wants to merge 1 commit into
masterfrom
worktree-salvage-marked-1770

Conversation

@martin-helmich

Copy link
Copy Markdown
Member

Salvages #1770. Dependabot's marked 15 → 17 bump has been stuck since April: marked-terminal@7.3.0 (its latest release) still declares a marked >=1 <16 peer dependency, so the "dependencies are resolvable" CI job (npm install) fails to resolve. yarn is lenient about the peer mismatch, which is why compile/lint/test passed there while the npm check stayed red.

What this does

  • Bumps marked to ^17.0.6.
  • Adds an npm overrides entry so npm install accepts marked 17 for marked-terminal, unblocking the resolvable-deps check.

Why it's safe

  • marked-terminal 7.3.0 renders correctly against marked 17 at runtime. I exercised the exact conversation show render path (marked.setOptions({ renderer: new TerminalRenderer() }) + await marked(md)) and headings, bold, italic, inline/fenced code, lists, blockquotes and links all render with correct ANSI output.
  • Upstream marked-terminal has no release that widens the peer range — even its master branch only goes to <17, and the issue tracking this (markedjs/marked-terminal#375) has been open since January with no maintainer response — so waiting on Dependabot alone will never turn this green.
  • Verified npm install now resolves cleanly (no --legacy-peer-deps), and yarn lint, yarn compile, and yarn test all pass.

Once this merges, #1770 can be closed.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E63yC1mME5QCHpCyfDmAD6

Dependabot's bump (#1770) has been stuck since April because
marked-terminal@7.3.0 (the latest release) still declares a
`marked >=1 <16` peer dependency, so `npm install` fails to resolve
in CI even though yarn is lenient about it.

marked-terminal 7.3.0 renders correctly against marked 17 at runtime
(verified against the conversation-show render path: headings, bold,
italic, inline/fenced code, lists, blockquotes and links all work),
and upstream has no release that widens the peer range (see
markedjs/marked-terminal#375).

Add an npm `overrides` entry so `npm install` accepts marked 17 for
marked-terminal, unblocking the "dependencies are resolvable" check.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E63yC1mME5QCHpCyfDmAD6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant