Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

services/horizon: Use UNIX timestamps instead of RFC3339 strings for timebounds. #4361

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Clarify data type in changelog
Co-authored-by: Leigh McCulloch <351529+leighmcculloch@users.noreply.github.com>
Shaptic and leighmcculloch authored Apr 30, 2022
commit 352a8cc03e1dc339401c87d166842d26e98fdd6d
2 changes: 1 addition & 1 deletion services/horizon/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -11,7 +11,7 @@ This is the final release after the [release candidate](v2.17.0-release-candidat
* `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)

- Timebounds within the `preconditions` object are a string representing UNIX timestamps in seconds rather than formatted date-times (which was a bug) ([4361](https://github.com/stellar/go/pull/4361)).
- Timebounds within the `preconditions` object are a string containing int64 UNIX timestamps in seconds rather than formatted date-times (which was a bug) ([4361](https://github.com/stellar/go/pull/4361)).

## V2.17.0 Release Candidate