Repository navigation
Prepare the Common 3 PCZT release - #210
Merged
Merged
Conversation
p0mvn
marked this pull request as ready for review
October 15, 2026 00:22
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
The published PCZT release still depends on Common 2, while the wallet source now uses Common 3. Reusing its version would make the publisher skip the updated package and leave consumers resolving the old cryptography types.
Prepare a new PCZT release candidate and update the backend and facade requirements, generated workspace, lockfile and dependency example together. Move the Common 3 and Rust 1.97 notes into the dated wallet release entries.
Breaking changes
This preparation adds no runtime or database changes. The new PCZT release carries the already merged Common 3 public types and Rust 1.97 minimum; consumers must use the matching wallet dependency family.
Validation
Release tooling tests and formatting pass, including the internal version and dependency order checks. All selected release crates passed full package verification together without uploading. Repository CI is pending. Registry upload and authentication will be exercised separately through the protected release workflow after merge.
Repairs: #184