release: explorer SDK 5.0.1 transaction chain validation - #192
Merged
Merged
Conversation
fix(connect): pin explorer and example to SDK 5.0.1
Contributor
Author
|
Release review: main...dev is the same independently reviewed three-file dependency/example update from PR #191. Local clean-install, all 575 tests, lint, TypeScript, formatting, API drift, and full production build gates pass. Staged release includes only the frontend, preserves the API/synchronizer and database, and retains the previous frontend for rollback. |
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
Pin the explorer and hosted dApp example to QRL Connect 5.0.1. This patch accepts an explicitly pinned transaction chain ID and revalidates queued transactions against the current account and network before transport.
Validation
Release scope
Frontend rebuild and restart only. No database, API, synchronizer, network or reverse-proxy changes. Existing chain and genesis guards remain enabled. The optional contract verifier retains its existing fail-closed availability state.