chore: release v1.3.0 - #92
Merged
Merged
Conversation
Adds `.github/workflows/release.yml`, which runs `cargo publish` to crates.io on the `release: published` event — the same trigger as the existing `npm-publish.yml`, so a single `gh release create` fans out to both registries. Why automate: publishing from a clean CI checkout (rather than a local working tree) structurally prevents the untracked-file leak class behind the v1.2.1 incident — `cargo publish --allow-dirty` can no longer bundle local state because CI has none. The job also guards the "one version, N places" rule by failing if the release tag does not match the `Cargo.toml` version, and uses `--locked` for a reproducible publish. Requires the `CARGO_REGISTRY_TOKEN` repository secret. Updates the Release Management section of CLAUDE.md to document the new flow (the GitHub release is the single publish trigger; do not run `cargo publish` locally) and reframes the pre-publish safety checks as a manual-escape-hatch concern now that the normal flow is CI-based. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Yonghye Kwon <developer.0hye@gmail.com>
Minor bump (1.2.2 -> 1.3.0): #91 added opt-in comment extraction for DOCX and PPTX — a new public `ConversionOptions.extract_comments` field and a `--extract-comments` CLI flag — which is new, non-breaking public API per SemVer. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Yonghye Kwon <developer.0hye@gmail.com>
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
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
Release v1.3.0 (minor) and enable automated publishing via GitHub Actions.
This bundles two related changes needed to cut the release through CI:
chore: release v1.3.0— bumpCargo.toml/Cargo.lockfrom1.2.2→1.3.0.ci: add automated crates.io publish on GitHub release— new.github/workflows/release.yml.Why minor
PR #91 added opt-in comment extraction for DOCX/PPTX: a new public
ConversionOptions.extract_commentsfield and a--extract-commentsCLI flag. New, non-breaking public API → SemVer minor.Automated publishing
release.ymlrunscargo publishto crates.io on therelease: publishedevent — the same trigger as the existingnpm-publish.yml, so onegh release create vX.Y.Zfans out to both crates.io and npm.cargo publishto bundle.Cargo.tomlversion, enforcing the "one version, N places" rule.cargo publish --locked.CARGO_REGISTRY_TOKENrepository secret.CLAUDE.md's Release Management section is updated to document the new flow.
Key changes
Cargo.toml,Cargo.lock: version1.2.2→1.3.0.github/workflows/release.yml(new): crates.io publish on releaseCLAUDE.md: release procedure now triggers automated publish; pre-publish safety checks reframed as a manual-escape-hatch concernVerification
cargo build --lockedpasses locally (Cargo.lock consistent with the bumped version). Full matrix + WASM + security checks run in CI on this PR.🤖 Generated with Claude Code