Repository navigation
v1.3.2
SDK v1.3.2 Release Notes
Version 1.3.2 introduces support for new license types, standardizes dispute handling, and simplifies transaction flows with auto-await behavior. It also includes key architectural improvements, such as unified option handling and stricter chainId typing. Some changes require updates to existing implementations. See the Migration Guide below for details.
Features & Enhancements
- Adds the
registerCreativeCommonsAttributionPILfunction to theLicensemodule. PR(#515) - Refactored the
Licensemodule to support the registration of multiple license types by extracting shared logic into a commonregisterPILTermsHelpermethod. PR(#515) - The Royalty module now returns
claimedTokenswhenclaimAllRevenueis called from a non-owner account PR(#526) - All transactions are now automatically awaited; waitForTransaction is no longer supported or required. This simplifies transaction handling, avoids issues with multi-TX flows, and improves the default developer experience. PR(#548)
Breaking Changes
- Updates the
RaiseDisputeRequestenum in theDisputemodule so it can be used instead of a string for thetargetTagproperty. PR(#521) - In the Royalty module,
royaltyVaultIpIdwas renamed toipId. PR(#523) - Improves
chainIdhandling by changing its type fromstringtonumberand updating how getPermissionSignature and getSignature retrieve it. PR(#527) - The
txHashfield in all modules has changed fromstringtoHash. PR(#545) - Consolidates all option parameters (e.g.,
wipOptions,erc20Options) into a single optional options object. All public client methods that accept options now use this unified property. PR(#547)
Migration Guide
Migrating from v1.2.x
- Please refer to the 1.3.0-rc.1 release notes.
Migration from v1.3.x
- Change the
chainIdparameter type toChainIdsin thegetPermissionSignatureandgetSignaturemethods, replacing the previousstring | number | bigint type. - Update the
ChainIdsdefinition from string literals("1315" | "1514")to numeric literals(1315 | 1514)when initializing the Story client. - In the Royalty module, when using the
ClaimableRevenueRequesttheroyaltyVaultIpIdfield should now beipId.
Old Syntax:
const x = await client.royalty.claimableRevenue({
royaltyVaultIpId: PARENT_IP_ID,
claimer: PARENT_IP_ID,
token: WIP_TOKEN_ADDRESS,
})New Syntax:
const x = await client.royalty.claimableRevenue({
ipId: PARENT_IP_ID,
claimer: PARENT_IP_ID,
token: WIP_TOKEN_ADDRESS,
})- Developers must now move
wipOptionsanderc20Optionsinto the unified options object when using client methods. Example:
Old syntax:
await client.ipAsset.batchRegisterIpAssetsWithOptimizedWorkflows({
requests: requests,
wipOptions: {
useMulticallWhenPossible: false,
},
});New syntax:
await client.ipAsset.batchRegisterIpAssetsWithOptimizedWorkflows({
requests: requests,
options: {
wipOptions: {
useMulticallWhenPossible: false,
},
},
});- In all modules, the
txHashfield must be changed from a string to a Hex.