Skip to content

Update dependency typedoc-plugin-markdown to v4.10.0 #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jakubno merged 1 commit into from
Mar 11, 2026
Merged

Update dependency typedoc-plugin-markdown to v4.10.0 #162

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/js-sdk/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"tsup": "^8.3.5",
"tsx": "^4.19.2",
"typedoc": "0.28.17",
"typedoc-plugin-markdown": "4.2.7",
"typedoc-plugin-markdown": "4.10.0",
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Align typedoc with plugin peer requirement

This change upgrades typedoc-plugin-markdown to 4.10.0 but leaves typedoc pinned to 0.26.8; the updated lockfile shows 4.10.0 now declares a typedoc: 0.28.x peer requirement (pnpm-lock.yaml:1575). Keeping this unsupported pair can break generate-ref/TypeDoc execution (and can fail installation where peer checks are enforced), so the dependency bump is incomplete unless typedoc is upgraded to a compatible 0.28.x release or the plugin stays on a 0.26.x-compatible version.

Useful? React with 👍 / 👎.

"typescript": "^5.6.3",
"vitest": "^3.0.5"
},
Expand Down
12 changes: 6 additions & 6 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading