release: @parity/truapi 0.7.0, @parity/truapi-host 0.4.0 - #332
Merged
Conversation
added 6 commits
August 4, 2026 07:29
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
pgherveou
enabled auto-merge
August 4, 2026 07:54
Imod7
approved these changes
Aug 4, 2026
filvecchiato
approved these changes
Aug 4, 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.
Release: @parity/truapi 0.7.0, @parity/truapi-host 0.4.0
Summary
This minor release ships the RFC-0022 mobile host cutover together with the completed RFC-0023 account VRF signing flow. It publishes the generated
AutoSigningKeyandSignVrfhost types, implements the Rust pairing-host API, persists product-scoped auto-signing keys, and requires Dotli confirmation before forwarding non-auto-signed requests to the paired Account Holder.Authorization behavior:
AutoSigninggrant signs locally without confirmation or a remote-SSO roundtripUserConfirmationReview::SignVrf; approval forwards it to the paired Account Holder for its own confirmation and signatureThe linked Dotli integration and structured confirmation UI are in paritytech/dotli-community#145.
Versions
@parity/truapi:0.6.0→0.7.0@parity/truapi-host:0.3.0→0.4.0@parity/truapi-hostdependency:@parity/truapi@^0.7.0Checklist
npm run version-packagesjs/packages/truapi/package.jsonis0.7.0js/packages/truapi-host/package.jsonis0.4.0@parity/truapi-hostdepends on@parity/truapi@^0.7.0rust/crates/truapi/Cargo.tomlandCargo.lockuse0.7.0.changeset/other thanconfig.jsonVerification
npm run check-release-versionscargo test -p truapi: 6 passed@parity/truapi: build and 203 tests passed@parity/truapi-host: build and 40 tests passedcargo test -p truapi-serversign_vrfauthorization tests: 5 passedmake e2e-dotli: 44 successful, 21 expected/allowlisted outcomes;Account/sign_vrfshowed the Dotli confirmation first, then passed through the paired signing-host CLI approval and returned a signature