chore(release): bump workspace versions to 0.9.1#113
Merged
stevenobiajulu merged 2 commits intomainfrom Apr 28, 2026
Merged
Conversation
Patch release covering bug fixes accumulated since v0.9.0: - fix(docx-core): merge auxiliary parts in rebuild mode (#94, #101) - fix(docx-core): emit paragraph-level markers outside <w:r> on rebuild (#109) - fix(docx-core): preserve reply comments in rebuild mode (#108, #112) - test(docx-mcp): harden vitest path allowlist against /tmp symlink topology (#105) - ci: SHA-pin all GitHub Actions, add dependency review and Dependabot - ci: fix PR title check for acronyms and fork PRs (#88) - chore(skills): sync docx-editing to 0.3.0 (#95) Generated via scripts/bump_version.mjs.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The bumped package-lock.json regenerated cleanly and exposed a latent bug: docx-mcp directly imports @xmldom/xmldom in tag_parser.ts but did not declare it as a dependency. It was previously masked by npm hoisting from docx-core's transitive dep — the workspace happened to work because the lockfile carried a stale hoisted xmldom@0.8.11. Pinning to ^0.8.11 (matching what was already running in production via the silent hoist) preserves observable behavior. tag_parser depends on xmldom 0.8's lenient parsing of cross-nested tags (<b><i>text</b></i>) — xmldom 0.9 throws on such input. Migrating docx-mcp's tag_parser to xmldom 0.9 is its own concern; this commit keeps the 0.9.1 release a pure version bump. docx-core continues to use xmldom ^0.9.9 (PR #75); the two versions coexist under their respective package's node_modules. No DOM nodes cross the docx-core/docx-mcp boundary, so the version split is safe.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Patch release covering bug fixes accumulated since v0.9.0.
Included fixes
fix(docx-core): merge auxiliary parts in rebuild mode — 文件比对功能异常，比对完成后附件打不开。 #94 (PR fix(docx-core): merge auxiliary parts in rebuild mode (#94) #101)fix(docx-core): emit paragraph-level markers outside<w:r>on rebuild — fix(docx-core): emit paragraph-level markers outside <w:r> on rebuild #109fix(docx-core): preserve reply comments in rebuild mode — Reply comments dropped in rebuild mode (mergeCommentAncillaryParts only walks root comments) #108 (PR fix(docx-core): preserve reply comments in rebuild mode (#108) #112)test(docx-mcp): harden vitest path allowlist against /tmp symlink topology — test(docx-mcp): harden vitest path allowlist against /tmp symlink topology #105ci: SHA-pin all GitHub Actions, add dependency review and Dependabotci: fix PR title check for acronyms and fork PRs — ci: fix PR title check for acronyms and fork PRs #88chore(skills): sync docx-editing to 0.3.0 — chore(skills): sync docx-editing to 0.3.0 matching ClawHub #95Generated via
scripts/bump_version.mjs.Test plan
node scripts/bump_version.mjs --checkreports all 12 files at 0.9.1v0.9.1on main → release workflow auto-publishes