Skip to content
Merged
Changes from all commits
Commits
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 package.json
Original file line number Diff line number Diff line change
Expand Up @@ -166,7 +166,7 @@
"vitest": "^3.2.4",
"vue": "^3.5.21",
"vue-i18n": "^11.1.11",
"vue-renderer-markdown": "0.0.55-beta.2",
"vue-renderer-markdown": "0.0.56-beta.4",
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Update pnpm-lock.yaml to keep dependency graph consistent.

Bumping vue-renderer-markdown here is good, but pnpm relies on the lockfile to pin the actual resolved version. Without updating pnpm-lock.yaml, installs will stay on the old 0.0.55-beta.2 (or trigger identity mismatches in CI). Please regenerate and commit the lockfile so the new renderer ships reliably.

🤖 Prompt for AI Agents
In package.json around lines 169 to 169, you've updated vue-renderer-markdown to
0.0.56-beta.4 but did not update pnpm-lock.yaml; regenerate and commit the
lockfile so installs use the bumped version. Run pnpm install (or pnpm install
--lockfile-only) to refresh pnpm-lock.yaml, verify the resolved
vue-renderer-markdown entry shows 0.0.56-beta.4, run the test/build CI steps
locally, and commit the updated pnpm-lock.yaml alongside this package.json
change.

"vue-router": "4",
"vue-sonner": "^2.0.8",
"vue-tsc": "^2.2.12",
Expand Down