Releases: stellar/js-stellar-base
v13.0.1
v13.0.0
v13.0.0
: Protocol 22.
This version is unchanged from beta.1
, whose changelog is replicated below.
Breaking Changes
- XDR definitions have been upgraded to Protocol 22 (#777).
Added
- You can create contracts with constructors a new, optional parameter of
Operation.createCustomContract
,constructorArgs: xdr.ScVal[]
(#770).
v13.0.0-beta.1
v13.0.0-beta.1
: Protocol 22
This is the first release that supports Protocol 22. While the network has not upgraded yet, you can start integrating the new features into your codebase if you want a head start. Keep in mind that while the binary XDR is backwards-compatible, the naming and layout of structures is not. In other words, this build will continue to work on Protocol 21, but you may have to update code that references XDR directly.
Breaking Changes
Added
- You can create contracts with constructors via a new, optional parameter of
Operation.createCustomContract
,constructorArgs: xdr.ScVal[]
(#770).
Full Changelog: v12.1.1...v13.0.0-beta.1
v12.1.1
v12.1.1
Fixed
- Add missing methods to TypeScript definitions (#766).
- Fix the TypeScript definition of
walkInvocationTree
to allow void returns on the callback function as intended rather than forcing areturn null
(#765). - Fix
authorizeEntry
to use the correct public key when passingKeypair
s (#772). - Upgrade misc. dependencies (#771, #773, #775).
Contributors
Full Changelog: v12.1.0...v12.1.1
v12.1.0
Added
TransactionBuilder
now hasaddOperationAt
andclearOperationAt
methods to allow manipulation of individual operations (#757).
Fixed
- Improve the efficiency and portability of asset type retrieval (#758).
nativeToScVal
now correctly sorts maps lexicographically based on the keys to match what the Soroban environment expects (#759).humanizeEvents
now handles events without acontractId
set more reliably (#764).nativeToScVal
now allows all integer types to come from strings (#763).
New Contributors
Full Changelog: v12.0.1...v12.1.0
v12.0.1
v12.0.1
Fixed
- Export TypeScript definition for
StrKey.isValidContract
(#751). scValToNative
would fail when the values contained error codes because the parsing routine hadn't been updated to the new error schemas. Errors are now converted to the following format (#753):
interface Error {
type: "contract" | "system";
code: number;
value?: string; // only present for type === 'system'
}
You can refer to the XDR documentation for additional explanations for each error code.
New Contributors
Full Changelog: v12.0.0...v12.0.1
v12.0.0
Protocol 21: Stable Release
This is exactly the same as v12.0.0-rc.1 with only dependency upgrades, but the full changelog from the previous stable version is replicated below.
Breaking Changes
- The generated XDR has been upgraded to match the upcoming Protocol 21, namely stellar/stellar-xdr@
1a04392
(#738).
Added
- To facilitate serialization and deserialization for downstream systems, this package now exports
cereal.XdrWriter
andcereal.XdrReader
which come directly from@stellar/js-xdr
(#744).
Fixed
- Updated various dependencies (#737, #739).
Buffer
andUint8Array
compatibility has improved inStrKey
(#746).
New Contributors
- @kanwalpreetd made their first contribution in #745
- @jiqiang90 made their first contribution in #746
Full Changelog: v11.0.1...v12.0.0
v12.0.0-rc.1
Protocol 21
Breaking Changes
- The generated XDR has been upgraded to match the upcoming Protocol 21, namely stellar/stellar-xdr@
1a04392
(#738).
Added
- To facilitate serialization and deserialization for downstream systems, this package now exports
cereal.XdrWriter
andcereal.XdrReader
which come directly from@stellar/js-xdr
(#744).
Fixed
- Updated various dependencies (#737, #739).
Buffer
andUint8Array
compatibility has improved inStrKey
(#746).
New Contributors
- @kanwalpreetd made their first contribution in #745
- @jiqiang90 made their first contribution in #746
Full Changelog: v11.0.1...v12.0.0-rc.1
v11.0.1
v11.0.0
Note: This version is (still) compatible with Protocol 20. Most people should be unaffected by the technically-breaking changes below and can treat this more like a v10.0.3 patch release.
Breaking Changes
- Starting from v10.0.0-beta.0, we set
BigNumber.DEBUG
inbignumber.js
totrue
internally, which affects all code usingBigNumber
. This behavior has been fixed and only affects this library: globally,BigNumber.DEBUG
now remains at its default setting (i.e. disabled). This is technically a breaking behavior change and is released as such (#729).
Fixed
Full Changelog: v10.0.2...v11.0.0