v1.0.2

Fix a bug where sodium-native was incorrectly being bundled with the browser release.

v1.0.1

Restore the old Operations.manageOffer and Operations.createPassiveOffer functions. They now issue a deprecation warning and return the value of the new operations calls.

v1.0.0

Because we're launching two breaking changes, we're taking the opportunity to switch to true semver! 🎉

• Breaking change Stellar Protocol 11 compatibility
  • Rename Operation.manageOffer to Operation.manageSellOffer.
  • Rename Operation.createPassiveOffer to Operation.createPassiveSellOffer.
  • Add Operation.manageBuyOffer.
• Breaking change The fee parameter to TransactionBuilder is now
  required. Failing to provide a fee will throw an error.

v0.13.2

• Bring DefinitelyTyped definitions into the repo for faster updating.
• Add missing Typescript type definitions.
• Add code to verify signatures when added to transactions.
• Replace ed25519 with sodium-native.
• Fix the xdr for SCP_MESSAGE.
• Update the README for the latest info.

v0.13.1

• Deploy to NPM with an env variable, not the Travis-encrypted key
• Cache node_modules in Travis

v0.13.0

• Remove the crypto library. This reduces the number of Node built-ins we have
  to shim into the production bundle, and incidentally fixes a bug with
  Angular 6.

v0.12.0

• Warning: Calling TransactionBuilder without a fee param is now deprecated
  and will issue a warning. In a later release, it will throw an error. Please
  update your transaction builders as soon as you can!
• Add a toXDR function for transactions that lets you get the transaction as a
  base64-encoded string (so you may enter it into the Stellar Laboratory XDR
  viewer, for one)
• Fix TransactionBuilder example syntax errors
• Use more thorough "create account" documentation
• Add Date support for TransactionBuilder timebounds
• Add two functions to Transaction that support pre-generated transactions:
  • getKeypairSignature helps users sign pre-generated transaction XDRs
  • addSignature lets you add pre-generated signatures to a built transaction

v0.11.0

• Added ESLint and Prettier to enforce code style
• Upgraded dependencies, including Babel to 6
• Bump local node version to 6.14.0
• Change Operations._fromXDRAmount to not use scientific notation (1e-7) for
  small amounts like 0.0000001.

v0.10.0

• Breaking change Added TransactionBuilder.setTimeout method that sets timebounds.max_time on a transaction. Because of the distributed nature of the Stellar network it is possible that the status of your transaction will be determined after a long time if the network is highly congested. If you want to be sure to receive the status of the transaction within a given period you should set the TimeBounds with maxTime on the transaction (this is what setTimeout does internally; if there's minTime set but no maxTime it will be added). Call to TransactionBuilder.setTimeout is required if Transaction does not have max_time set. If you don't want to set timeout, use TimeoutInfinite. In general you should set TimeoutInfinite only in smart contracts. Please check TransactionBuilder.setTimeout docs for more information.
• Fixed decoding empty homeDomain.

v0.9.0

• Update js-xdr to support unmarshaling non-utf8 strings.
• String fields returned by Operation.fromXDRObject() are of type Buffer now (except SetOptions.home_domain and ManageData.name - both required to be ASCII by stellar-core).