-
Notifications
You must be signed in to change notification settings - Fork 499
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
ingest/ledgerbackend: Add version check for protocol 21 #5346
ingest/ledgerbackend: Add version check for protocol 21 #5346
Conversation
4c36e8e
to
b32aad8
Compare
you can also remove protocol 20 from the integration tests matrix https://github.com/stellar/go/blob/master/.github/workflows/horizon.yml#L16 |
@urvisavla I think you meant to say "Removing checks for core versions older than protocol 21," right? |
yes, thank you. |
e9de3a2
to
2fbbde2
Compare
…ol version and update ledgerexporter and captivecorebackend to use these shared functions. Implement a version check for protocol 21 when creating a new captive-core instance.
2fbbde2
to
ffc70d0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks for considering the suggeestions.
PR Checklist
PR Structure
otherwise).
services/friendbot
, orall
ordoc
if the changes are broad or impact manypackages.
Thoroughness
.md
files, etc... affected by this change). Take a look in the
docs
folder for a given service,like this one.
Release planning
needed with deprecations, added features, breaking changes, and DB schema changes.
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
Added shared functions to get the stellar-core build version and protocol version:
GetCoreBuildVersion
GetCoreProtocolVersion
Updated ledgerexporter and captivecorebackend to use these shared functions to get stellar-core build version.
Implemented a version check for protocol 21 when creating a new captive-core instance.
Why
We previously had the core build for Soroban in several places. Now that we're on protocol 21, we should check the protocol version instead of the core build version. For more details, see #5333.
Known limitations
Any system using captive-core will not be compatible with stellar-core versions older than 21.