Releases: stellar/go
horizonclient & txnbuild v1.0
This is the first release of horizonclient, a completely reworked Go Horizon SDK client for the Stellar network. Check out the README for more info!
This is also the first release of txnbuild, a new package for building transactions and operations. Check out the README for more info!
Together, these two packages provide a complete Horizon SDK in Go.
Horizon v0.17.5
- Support for stellar-core v11.0.0.
- Display trustline authorization state in the balances list.
- Improved actions code.
- Improved
horizon db reingest
command handling code. - Tracking app name and version that connects to Horizon (
X-App-Name
,X-App-Version
).
Horizon v0.17.4
- Add support for compatibility with Stellar-Core 10.3.0 (new database schema v9).
- Fix a bug in
horizon db reingest
command (no log output). - Multiple code improvements and bug fixes.
Horizon v0.17.4 rc2
Release Candidate. Do not use in production.
Horizon v0.17.4 rc1
Release Candidate. Do not use in production.
Horizon v0.17.3
- Fix a bug in
txsub
package that caused returning invalid status when resubmitting old transactions (#969).
Horizon v0.17.2
- Critical fix bug
Horizon v0.17.1
Critical!
This release contains a critical bug! Please upgrade directly to 0.17.2.
- Fixes high severity error in ingestion system.
- Account detail endpoint (
/accounts/{id}
) includeslast_modified_ledger
field for account and for each non-native asset balance.
Horizon v0.16.1
- Fixes high severity error in ingestion system.
Horizon v0.17.0
Critical!
This release contains a critical bug! Please upgrade directly to 0.17.2.
Upgrade notes
This release introduces ingestion of failed transactions. This feature is turned off by default. To turn it on set environment variable: INGEST_FAILED_TRANSACTIONS=true
or CLI param: --ingest-failed-transactions=true
. Please note that ingesting failed transactions can double DB space requirements (especially important for full history deployments).
Database migration notes
Previous versions work fine with new schema so you can migrate (horizon db migrate up
using new binary) database without stopping the Horizon process. To reingest ledgers run horizon db reingest
using Horizon 0.17.0 binary. You can take advantage of the new horizon db reingest range
for parallel reingestion.
Deprecations
/operation_fee_stats
is deprecated in favour of/fee_stats
. Will be removed in v0.18.0.
Breaking changes
- Fields removed in this version:
- Root >
protocol_version
, usecurrent_protocol_version
andcore_supported_protocol_version
. - Ledger >
transaction_count
, usesuccessful_transaction_count
andfailed_transaction_count
. - Signer >
public_key
, usekey
.
- Root >
- This Horizon version no longer supports Core <10.0.0. Horizon can still ingest version <10 ledgers.
- Error event name during streaming changed to
error
to follow W3C specification.
Changes
- Added ingestion of failed transactions (see Upgrade notes). Use
include_failed=true
GET parameter to display failed transactions, operations and payments in collection endpoints. Single transaction endpoints (/transactions/{id}
,/transactions/{id}/operations
and/transactions/{id}/payments
) display information even if a transaction is failed so it's important to checksuccessful
andtransaction_successful
fields. /fee_stats
endpoint has been extended with fee percentiles and ledger capacity usage. Both are useful in transaction fee estimations.- Fixed a bug causing slice bounds out of range at
/account/{id}/offers
endpoint during streaming. - Added
horizon db reingest range X Y
that reingests ledgers between X and Y sequence number (closed intervals). - Many code improvements.