v10.2.0

v10.2.0

Fix

• Adds the missing successful field to transaction responses (#790).

Update

• Bumps stellar-base version to v8.1.0 to include bug fixes and latest XDR changes.

v10.1.2

Fix

• Upgrades the eventsource dependency to fix a critical security vulnerability (#783).

v10.1.1

Fixes

• Reverts a change from v10.1.0 which caused streams to die prematurely (#780).
• Bumps stellar-base version to v8.0.1 to include latest bugfixes.

Full Changelog: v10.1.0...v10.1.1

v10.1.0

This is a promotion without changes from v10.1.0-beta.0. Its CHANGELOG is replicated below.

Add

• Support for Protocol 19 (#775):

  • new precondition fields on a TransactionResponse
  • new account fields on AccountResponse and AccountRecord
  • bumping stellar-base to the latest beta version

• Add a way to filter offers by seller: OfferCallBuilder.seller(string), corresponding to GET /offers?seller=<string> (#773).

Fix

• Add missing field to account responses: last_modified_time which is the time equivalent of the existing last_modified_ledger (#770).

• Stop opening extra connections when SSE streams receive event: close events (#772).

• Fix SSE streams not loading under React Native (thank you, @hunterpetersen!) (#761).

v10.1.0-beta.0

v10.1.0-beta.0

Add

• Support for Protocol 19 (#775):

  • new precondition fields on a TransactionResponse
  • new account fields on AccountResponse and AccountRecord
  • bumping stellar-base to the latest beta version

• Add a way to filter offers by seller: OfferCallBuilder.seller(string), corresponding to GET /offers?seller=<string> (#773).

Fix

• Add missing field to account responses: last_modified_time which is the time equivalent of the existing last_modified_ledger (#770).

• Stop opening extra connections when SSE streams receive event: close events (#772).

• Fix SSE streams not loading under React Native (thank you, @hunterpetersen!) (#761).

v10.0.1

Fix

• Add missing fields to the LedgerRecord: successful_transaction_count and failed_transaction_count (#740). Note that this also marks several fields as deprecated because they don't actually exist in the Horizon API response:

  • transaction_count: superceded by the sum of the aforementioned fields
  • base_fee: superceded by the base_fee_in_stroops field
  • base_reserve: superceded by the base_reserve_in_stroops field

These deprecated fields will be removed in the next major version. It's unlikely that this breaking change should affect anyone, as these fields have likely been missing/invalid for some time.

Update

• Update a number of dependencies that needed various security updates:

  • several dependencies bumped their patch version (#736, #684, #672, #666, #644, #622)
  • axios has been bumped to 0.25.0 without causing breaking changes (#742)
  • the karma suite of packages has been updated to the latest major version (#743)

All of the dependencies in question besides axios were developer dependencies, so there never was downstream security impact nor will there be downstream upgrade impact.

v10.0.0

This release introduces breaking changes from stellar-base. It adds unconditional support for muxed accounts. Please refer to the corresponding release notes for details on the breaking changes there.

Breaking Updates

• Upgrades the stellar-base library to v7.0.0 (#735).

• Removes the AccountResponse.createSubaccount method since this is also gone from the underlying Account interface. The stellar-base release notes describe alternative construction methods (#735).

Fix

• Use the right string for liquidity pool trades (#734).

v9.1.0

Add

• Adds a way to filter liquidity pools by participating account: server.liquidityPools.forAccount(id) (#727).

Updates

• Updates the following SEP-10 utility functions to include client domain verification functionality (#720):

  • Utils.buildChallengeTx() accepts the clientDomain and clientSigningKey optional parameters
  • Utils.readChallengeTx() parses challenge transactions containing a client_domain ManageData operation
  • Utils.verifyChallengeTxSigners() verifies an additional signature from the clientSigningKey keypair if a client_domain Manage Data operation is included in the challenge

• Bumps stellar-base version to v6.0.6.

Fix

• Fixes the type_i enumeration field to accurately reflect liquidity pool effects (#723).

• Upgrades axios dependency to v0.21.4 to alleviate security concern (GHSA-cph5-m8f7-6c5x, #724).

• Publish Bower package to stellar/bower-js-stellar-sdk (#725).

v9.0.1

This SDK release supports Protocol 18.

You should upgrade to the latest version of this SDK as soon as possible: it is required for full compatibility once Protocol 18 is live. There are changes to Stellar's binary protocol that are not backwards compatible, and earlier versions may soon provide an incomplete or broken picture of the network.

For a comprehensive list of changes to the library, you can refer to the notes for the pre-release versions:

• v9.0.0-beta.0
• v9.0.0-beta.1

Changes in this version since the last beta release are as follows:

• Corrects the reserves field on LiquidityPoolRecords to be an array (#715).
• Bumps the stellar-base dependency to v6.0.4 (#715).

v9.0.0-beta.1

This beta release adds support for Automated Market Makers. For details, you can refer to CAP-38 for XDR changes and this document for detailed changes to the Horizon API.

Add

• Add /liquidity_pools/:id/trades endpoint (#710)

Updates

• Updates the following SEP-10 utility functions to be compilant with the protocols (#709, stellar-protocol/#1036)
  • Updated utils.buildChallengeTx() to accept muxed accounts (M...) for client account IDs
  • Updated utils.buildChallengeTx() to accept a memo parameter to attach to the challenge transaction
  • Updated utils.readChallengeTx() to provide a memo property in the returned object
  • Updated utils.readChallengeTx() to validate challenge transactions with muxed accounts (M...) as the client account ID

Fix

• Drops the chai-http dependency to be only for developers (#707).