@parity/product-sdk 0.27.0 → 0.28.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@parity/product-sdk",
-  "version": "0.27.0",
+  "version": "0.28.0",
   "description": "Unified SDK for building products in the Polkadot ecosystem - umbrella package",
   "type": "module",
   "sideEffects": false,
@@ -72,19 +72,19 @@
   "dependencies": {
     "polkadot-api": "^2.1.6",
     "@parity/product-sdk-address": "0.2.0",
+    "@parity/product-sdk-cloud-storage": "0.12.0",
+    "@parity/product-sdk-chain-client": "0.12.4",
     "@parity/product-sdk-crypto": "0.1.1",
-    "@parity/product-sdk-individuality": "0.4.0",
-    "@parity/product-sdk-contracts": "0.10.7",
-    "@parity/product-sdk-host": "0.19.1",
-    "@parity/product-sdk-chain-client": "0.12.3",
-    "@parity/product-sdk-keys": "0.3.24",
+    "@parity/product-sdk-host": "0.20.0",
+    "@parity/product-sdk-contracts": "0.10.8",
+    "@parity/product-sdk-individuality": "0.5.0",
+    "@parity/product-sdk-keys": "0.3.25",
     "@parity/product-sdk-logger": "0.1.1",
-    "@parity/product-sdk-signer": "0.14.4",
-    "@parity/result": "0.2.0",
     "@parity/product-sdk-errors": "0.2.0",
-    "@parity/product-sdk-tx": "0.4.7",
-    "@parity/product-sdk-local-storage": "0.3.9",
-    "@parity/product-sdk-cloud-storage": "0.11.3"
+    "@parity/product-sdk-signer": "0.14.5",
+    "@parity/result": "0.2.0",
+    "@parity/product-sdk-local-storage": "0.3.10",
+    "@parity/product-sdk-tx": "0.4.8"
   },
   "peerDependencies": {
     "react": "^18.0.0 || ^19.0.0"

package/src/individuality/contract.test.ts

@@ -45,6 +45,7 @@ import type {
     GamePlayersChain,
     IndividualityChain,
     LegacySuffixChain,
+    LiteAliasBindChain,
     LiteSignUpChain,
     NetworkSuffixChain,
     PapiIndividualityChain,
@@ -133,23 +134,35 @@ type FromPapiSatisfiesContracts = Assert<
         : false
 >;
 
+// Storage is the only way either chain resolves a suffix since the re-pin, so the
+// bring-your-own-client path needs it asserted too.
+type FromPapiSatisfiesTheSuffixStorage = Assert<
+    PapiIndividualityChain<
+        PaseoClient["individuality"],
+        PaseoClient["raw"]["individuality"]
+    > extends NetworkSuffixChain
+        ? true
+        : false
+>;
+
 type PaseoSatisfiesScoreContext = Assert<PaseoClient extends ScoreContextChain ? true : false>;
 type DevnetSatisfiesScoreContext = Assert<DevnetClient extends ScoreContextChain ? true : false>;
 type PreviewnetSatisfiesScoreContext = Assert<
     PreviewnetClient extends ScoreContextChain ? true : false
 >;
 
-// Negative on purpose: a re-pin that flips either is the prompt to re-run the
-// read against that chain.
-type PreviewnetSatisfiesLegacySuffix = Assert<
-    PreviewnetClient extends LegacySuffixChain ? true : false
+// The suffix moved from a constant to storage upstream, and the 2026-09-03 re-pin
+// brought that to both live chains. Devnet still predates it, so it holds the old
+// shape and is the one asserted negatively now.
+type PreviewnetPredatesTheLegacySuffix = Assert<
+    PreviewnetClient extends LegacySuffixChain ? false : true
 >;
 type PaseoPredatesTheLegacySuffix = Assert<PaseoClient extends LegacySuffixChain ? false : true>;
 type DevnetPredatesTheLegacySuffix = Assert<DevnetClient extends LegacySuffixChain ? false : true>;
-type PreviewnetHasNoSuffixStorage = Assert<
-    PreviewnetClient extends NetworkSuffixChain ? false : true
+type PreviewnetHasSuffixStorage = Assert<
+    PreviewnetClient extends NetworkSuffixChain ? true : false
 >;
-type PaseoHasNoSuffixStorage = Assert<PaseoClient extends NetworkSuffixChain ? false : true>;
+type PaseoHasSuffixStorage = Assert<PaseoClient extends NetworkSuffixChain ? true : false>;
 type DevnetHasNoSuffixStorage = Assert<DevnetClient extends NetworkSuffixChain ? false : true>;
 
 // The two are declared separately, so a rename on either side would go
@@ -409,14 +422,38 @@ type LiteSignUpReadBase = GameChain & SignUpChain & ScoreContextChain & LiteSign
 type PaseoSatisfiesTheLiteReadWithATld = Assert<
     PaseoClient extends LiteSignUpReadBase ? true : false
 >;
-type PaseoCannotResolveTheSuffixItself = Assert<
-    PaseoClient extends LiteSignUpReadBase & LegacySuffixChain ? false : true
+// Both chains resolve the suffix from storage since the 2026-09-03 re-pin, so the
+// storage overload is the live path and neither can use the constant one.
+type PaseoSatisfiesTheLiteReadFromStorage = Assert<
+    PaseoClient extends LiteSignUpReadBase & NetworkSuffixChain ? true : false
+>;
+type PreviewnetSatisfiesTheLiteReadFromStorage = Assert<
+    PreviewnetClient extends LiteSignUpReadBase & NetworkSuffixChain ? true : false
 >;
-type PreviewnetSatisfiesTheLiteReadFromItsConstant = Assert<
-    PreviewnetClient extends LiteSignUpReadBase & LegacySuffixChain ? true : false
+type NeitherChainHasTheLegacyConstant = Assert<
+    PaseoClient | PreviewnetClient extends LiteSignUpReadBase & LegacySuffixChain ? false : true
 >;
 type DevnetPredatesTheLiteRead = Assert<DevnetClient extends LiteSignUpReadBase ? false : true>;
 
+// Wider than the reads above: the builder assembles the extrinsic itself, so it
+// needs the chain spec and the metadata blob, not just the call.
+type PaseoSatisfiesBindContract = Assert<PaseoClient extends LiteAliasBindChain ? true : false>;
+type PreviewnetSatisfiesBindContract = Assert<
+    PreviewnetClient extends LiteAliasBindChain ? true : false
+>;
+type DevnetSatisfiesBindContract = Assert<DevnetClient extends LiteAliasBindChain ? true : false>;
+type FromPapiSatisfiesBindContract = Assert<
+    PapiIndividualityChain<
+        PaseoClient["individuality"],
+        PaseoClient["raw"]["individuality"]
+    > extends LiteAliasBindChain
+        ? true
+        : false
+>;
+type RejectsBogusBindClient = Assert<
+    ClientWithoutIndividuality extends LiteAliasBindChain ? false : true
+>;
+
 // Pinned by name for the same reason `sign_up_with_account`'s are: PAPI encodes
 // the object it is handed, so a renamed field silently encodes as `undefined` —
 // and `account` here is a call argument, not implied by the signer.