Skip to content

fix(connect): pin explorer and example to SDK 5.0.1 - #191

Merged
moscowchill merged 2 commits into
devfrom
fix/connect-relay-chain-pin-20260921
Sep 21, 2026
Merged

moscowchill merged 2 commits into
devfrom
fix/connect-relay-chain-pin-20260921

Conversation

@moscowchill

Copy link
Copy Markdown
Contributor

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

  • Clean npm ci and audit: zero vulnerabilities.
  • All 575 frontend tests pass, including contract-write chain and genesis guards.
  • ESLint: zero errors and 14 existing warnings. TypeScript, Prettier, API drift and shell syntax checks pass.
  • Full production build and hosted example build from public tag v5.0.1 pass.
  • Published package integrity matches the independently tested release artifact.
  • Independent review of the three-file diff passed. No transitive dependency changes.

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.

@moscowchill

Copy link
Copy Markdown
Contributor Author

Independent review completed: the three-file diff only changes the exact SDK pin, registry artifact integrity, and hosted example tag. No transitive dependency churn or source findings. Local release gates pass: 575 tests, zero lint errors, TypeScript, Prettier, API drift, full production and hosted example builds, and zero audit vulnerabilities. Deployment remains frontend-only with the previous frontend retained for rollback.

@moscowchill
moscowchill merged commit 5b52ac6 into dev Sep 21, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant