Skip to content

Commit

Permalink
Mark changelog as ready for v2.17.0 w/ #4360
Browse files Browse the repository at this point in the history
  • Loading branch information
Shaptic committed Apr 30, 2022
1 parent df25775 commit ee9fccf
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions services/horizon/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,13 @@
All notable changes to this project will be documented in this
file. This project adheres to [Semantic Versioning](http://semver.org/).

## Unreleased
## V2.17.0

This is the final release after the [release candidate](v2.17.0-release-candidate), including some small additional changes:

- The transaction precondition record now excludes ([4360](https://github.com/stellar/go/pull/4360)):
* `min_account_sequence_age` when it's `"0"`, as this is the default value when the condition is not set
* `preconditions.ledgerbounds.max_ledger` when it's set to 0 (this means that there is no upper bound)

## V2.17.0 Release Candidate

Expand Down Expand Up @@ -40,7 +46,7 @@ file. This project adheres to [Semantic Versioning](http://semver.org/).
}
```

All of the top-level fields within this object are also optional. However, the "ledgerbounds" object will always have its inner values set.
All of the top-level fields within this object are also optional. However, the "ledgerbounds" object will always have at least its `max_ledger` field set.

Note that the existing "valid_before_time" and "valid_after_time" fields on the top-level object will be identical to the "preconditions.timebounds.min_time" and "preconditions.timebounds.min_time" fields, respectively, if those exist. The "valid_before_time" and "valid_after_time" fields are now considered deprecated and will be removed in Horizon v3.0.0.

Expand Down

0 comments on commit ee9fccf

Please sign in to comment.