services/horizon: Merge horizon v22.0.0 release branch into master #5522
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update protocol 22 branch with commits from master
…missionResponse` (#5445) * convert json to snake-case * change naming to snake-case - 2
Add logic to distinguish whether the response object is `AsyncTransactionSubmissionResponse` or `Horizon.Problem` and send response accordingly.
…5428) * Remove GetLedgerEntry to make breaking changes more visible * Add unit tests for POST, request body, response JSON
* Update .gitignore to ignore bucket-cache/ at any level * clean up all occurences of Amount and NumAccounts (#5438) * Cleanup validAfter and validBefore * Remove unused fn * Update fixture * SQL to drop columns for protocol 22 release * Remove amount and num_accounts from ExpAssetStats table and test fixtures * Remoce extra space in sql migration file. Generate bindata.go with gogenerate.sh * Update code to show only authorized accounts and balances in ticker service * Fix tests in ticker * Updated CHANGELOG.md to include breaking changes
Merge master to protocol 22 release branch
* Bump integration tests to soroban rpc rc3 * Remove flaky test to ensure units pass
2opremio
approved these changes
Nov 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
PR Structure
otherwise).
services/friendbot, orallordocif the changes are broad or impact manypackages.
Thoroughness
.mdfiles, etc... affected by this change). Take a look in the
docsfolder for a given service,like this one.
Release planning
CHANGELOG.mdwithin the component folder structure. For example, if I changed horizon, then I updated (services/horizon/CHANGELOG.md. I add a new line item describing the change and reference to this PR. If I don't update a CHANGELOG, I acknowledge this PR's change may not be mentioned in future release notes.semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
Merge the horizon v22.0.0 release branch back into master