chore(python): bump docx-scalpel to 0.1.0a4#214
Merged
Conversation
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.
Bumps
docx-scalpelto 0.1.0a4 so the next PyPI alpha ships the DOCX→HTML surface.The currently published alpha
0.1.0a3(tagdocx-scalpel-v0.1.0a3, commit #207) predates #212, soconvert_docx_to_html/DocxSession.to_htmlare not yet on PyPI. Taggingdocx-scalpel-v0.1.0a4after this merges will publish them (viapython-publish.yml).One-line
python/pyproject.tomlversion bump, mirroring #199 (a2) and #207 (a3). The publish workflow also pins pyproject to the tag version at build time, so this keeps the source-of-truth in sync.After merge
git tag -a docx-scalpel-v0.1.0a4 -m docx-scalpel-v0.1.0a4 <merged-sha> && git push origin docx-scalpel-v0.1.0a4→ publishes to production PyPI. (Docxodus core / NuGet unaffected — that's the separatev*tag.)