Repository navigation
chore(release): v0.3.2 - #54
Merged
Merged
Conversation
Srayman
approved these changes
Sep 30, 2026
|
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.



Includes
Note
Low Risk
Manifest and lockfile version bumps only; no runtime or API edits in this diff.
Overview
Summary
Cuts v0.3.2 release: workspace and client-facing crates get new semver tags so crates.io (and downstream
Cargo.tomlpins) pick up work merged in #53. This PR has no Rust source edits, only manifest and lockfile version lines.Related Issues
Refs #53
Changes Made
[workspace.package]version 0.3.0 → 0.3.2[workspace.dependencies]entries and Cargo.lock refreshTesting
cargo build --workspaceandcargo test --workspaceon the release branch; confirm published crate versions match the bumped manifests if you ship to crates.io.Breaking Changes
None
Reviewed by Cursor Bugbot for commit 843fc73. Configure here.