-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[Node upgrade] (Version: [2.1.0]) #4928
Comments
As for the breaking change, I see that they are all for api 2. so, how do we specify the version in the configuration? |
As already stated on https://github.com/XRPLF/rippled/releases/tag/2.1.0 :
No: in general you are not required to do something before you can upgrade. The API version is a field ( It is not part of the |
That's an amendment, not an actual breaking change. All amendments are technically breaking changes, but rarely change APIs. |
https://github.com/XRPLF/rippled/releases/tag/2.1.0
hi, team Is it compatible with previous versions?and once again, are there any RPC structure changes?
“ Breaking change (fix or feature that would cause existing functionality to not work as expected)” , I saw this description. does that require us to do something before we upgrade?
The text was updated successfully, but these errors were encountered: