chore: release v0.1.8 - #23
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 74fe49d83a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| officemd_pptx = { version = "0.1.7", path = "../officemd_pptx" } | ||
| officemd_pdf = { version = "0.1.7", path = "../officemd_pdf" } | ||
| officemd_markdown = { version = "0.1.7", path = "../officemd_markdown" } | ||
| officemd_docx = { version = "0.1.8", path = "../officemd_docx" } |
There was a problem hiding this comment.
Bump the Python package metadata for this release
When this release is tagged, the Python workflow builds wheels from crates/officemd_python/pyproject.toml, but that file still declares version = "0.1.6" while this commit moves the binding's Rust dependencies to the 0.1.8 crates. Because pypi-publish also uses skip-existing, the v0.1.8 release will either produce 0.1.6 wheels or skip publishing them instead of shipping the new Python package, so the pyproject version needs to be updated with the Rust release.
Useful? React with 👍 / 👎.
| officemd_pptx = { version = "0.1.7", path = "../officemd_pptx" } | ||
| officemd_pdf = { version = "0.1.7", path = "../officemd_pdf" } | ||
| officemd_markdown = { version = "0.1.7", path = "../officemd_markdown" } | ||
| officemd_docx = { version = "0.1.8", path = "../officemd_docx" } |
There was a problem hiding this comment.
Bump the npm package metadata for this release
The npm release job publishes the versions read from crates/officemd_js/package.json and npm/*/package.json, but those files still say 0.1.6 and the main package's optional dependencies still point at 0.1.6 while this commit links the JS binding against the 0.1.8 Rust crates. On a v0.1.8 release this will skip/re-publish 0.1.6 packages instead of producing installable 0.1.8 platform packages, so the npm package metadata needs to be kept in sync with these dependency bumps.
Useful? React with 👍 / 👎.
🤖 New release
officemd_markdown: 0.1.7 -> 0.1.8officemd_xlsx: 0.1.7 -> 0.1.8officemd_cli: 0.1.7 -> 0.1.8officemd_docx: 0.1.7 -> 0.1.8officemd_csv: 0.1.7 -> 0.1.8officemd_pptx: 0.1.7 -> 0.1.8officemd_pdf: 0.1.7 -> 0.1.8Changelog
officemd_docxofficemd_csvofficemd_pptxofficemd_pdfThis PR was generated with release-plz.