Skip to content

chore(release): prepare zstdscope-cli 0.3.0 - #50

Merged
tappe9 merged 1 commit into
mainfrom
chore/prepare-cli-v0.3.0
Aug 27, 2026
Merged

tappe9 merged 1 commit into
mainfrom
chore/prepare-cli-v0.3.0

Conversation

@tappe9

@tappe9 tappe9 commented Aug 27, 2026 •

Copy link
Copy Markdown
Owner

Summary

Prepare the v0.3.0 project release without publishing credentials or creating a tag.

  • version zstdscope-cli independently as 0.3.0;
  • keep zstdscope at the already-published 0.2.0 because parser behavior and the public Rust API are unchanged;
  • preserve the CLI dependency on released zstdscope 0.2.0, allowing all package/publish/install gates to run before publication;
  • add the v0.3.0 changelog, package-versioning ADR, release procedure, and aligned English/Japanese documentation;
  • move compressed-block structural metadata to the v0.4 roadmap milestone.

Release boundary

This PR performs every reversible repository-side preparation step. It intentionally does not:

  • publish to crates.io;
  • create or push v0.3.0;
  • create the GitHub Release.

Those irreversible/authenticated operations must be performed from a clean local checkout of the merged main, following docs/RELEASING.md.

Compatibility

  • zstdscope Rust API: unchanged (0.2.0)
  • parser/validation behavior: unchanged
  • human-readable CLI output: unchanged
  • zstdscope-cli: 0.3.0
  • CLI JSON: schema version 1; breaking relative to the source-built v0.2 CLI JSON because u64 values are decimal strings and schema_version is added

Versioning decision

The original shared workspace version was split because the packages now have independent contracts. Publishing an unchanged core solely to align numbers would be misleading, and pinning the CLI to an unreleased core 0.3.0 would prevent package-boundary publish/install validation before release. ADR 0007 records the decision.

Self-review

Reviewed the complete 10-file diff against the merged PR #49 behavior and release requirements.

  • no parser, validation, public Rust API, or renderer source changed;
  • root workspace version inheritance was removed and both package versions are explicit;
  • Cargo.lock contains zstdscope 0.2.0 and zstdscope-cli 0.3.0;
  • the CLI continues to use the exact released core API version it needs;
  • README/README.ja, ROADMAP, CHANGELOG, ADR 0007, and the release procedure state the package-version split consistently;
  • package smoke version extraction supports the new CLI version;
  • no unresolved PR comments, reviews, or review threads exist.

Validation

CI run #146 passed all six jobs at head 3bb5df1c24d779c7ba60d2dc097d0af38fb6d1cd:

  • cargo fmt --check
  • cargo clippy --workspace --all-targets --all-features --locked -- -D warnings
  • cargo test --workspace --all-features --locked
  • rustdoc with warnings denied
  • core no-default-features tests
  • wasm32-unknown-unknown core compile check
  • core package list and publish dry-run
  • CLI package list and publish dry-run
  • generated CLI package install, --version, text inspect, and schema-v1 JSON smoke
  • Rust 1.85.0 MSRV check/test
  • Ubuntu, Windows, and macOS tests
  • cargo-deny advisory/license/ban/source policy

Documentation

  • CHANGELOG.md
  • docs/RELEASING.md
  • ADR 0007: independent library and CLI package versions
  • README / README.ja
  • ROADMAP

@tappe9
tappe9 marked this pull request as ready for review August 27, 2026 05:09
@tappe9
tappe9 merged commit 32f48d3 into main Aug 27, 2026
6 checks passed
@tappe9
tappe9 deleted the chore/prepare-cli-v0.3.0 branch August 27, 2026 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant