Repository navigation
chore(release): prepare zstdscope-cli 0.3.0 - #50
Merged
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
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
Prepare the v0.3.0 project release without publishing credentials or creating a tag.
zstdscope-cliindependently as0.3.0;zstdscopeat the already-published0.2.0because parser behavior and the public Rust API are unchanged;zstdscope 0.2.0, allowing all package/publish/install gates to run before publication;Release boundary
This PR performs every reversible repository-side preparation step. It intentionally does not:
v0.3.0;Those irreversible/authenticated operations must be performed from a clean local checkout of the merged
main, followingdocs/RELEASING.md.Compatibility
zstdscopeRust API: unchanged (0.2.0)zstdscope-cli:0.3.0u64values are decimal strings andschema_versionis addedVersioning 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.0would 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.
Cargo.lockcontainszstdscope 0.2.0andzstdscope-cli 0.3.0;Validation
CI run #146 passed all six jobs at head
3bb5df1c24d779c7ba60d2dc097d0af38fb6d1cd:cargo fmt --checkcargo clippy --workspace --all-targets --all-features --locked -- -D warningscargo test --workspace --all-features --lockedwasm32-unknown-unknowncore compile check--version, text inspect, and schema-v1 JSON smokeDocumentation
CHANGELOG.mddocs/RELEASING.md