We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The checkStellarCoreMajorVersionProtocolIdentity check here was commented out in #3808, but needs to be re-enabled in a way that works.
checkStellarCoreMajorVersionProtocolIdentity
The text was updated successfully, but these errors were encountered:
would that check never work for vnext? Like when we release 20.0, vnext will want to have a protocol version that is 21
Sorry, something went wrong.
Yeah the check as-is is not what we want. This issue is about re-enabling the check in a way that works, or making sure it can stay removed.
Merge pull request #4321 from graydon/bug-3810-core-major-version-pro…
1bc57e7
…tocol-identity-check Fix #3810, re-enable checkStellarCoreMajorVersionProtocolIdentity Reviewed-by: sisuresh
80cdfad
graydon
Successfully merging a pull request may close this issue.
The
checkStellarCoreMajorVersionProtocolIdentity
check here was commented out in #3808, but needs to be re-enabled in a way that works.The text was updated successfully, but these errors were encountered: