[Node upgrade] (Version: [2.1.0])

[xiongjiabing]

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？

[mvadari]

Nope.

https://github.com/XRPLF/rippled/blob/develop/API-CHANGELOG.md

[xiongjiabing]

As for the breaking change, I see that they are all for api 2. so, how do we specify the version in the configuration？

[intelliot]

As already stated on https://github.com/XRPLF/rippled/releases/tag/2.1.0 :

• Yes, it is compatible with previous versions.
• There are no RPC structure changes.
• Where did you see “ Breaking change (fix or feature that would cause existing functionality to not work as expected)”?

No: in general you are not required to do something before you can upgrade.

The API version is a field (api_version) you can specify with each RPC request. For details on how to specify api_version, see: https://xrpl.org/request-formatting.html#api-versioning

It is not part of the rippled configuration (rippled.cfg); instead, it is a choice that RPC clients can make when sending requests.

[xiongjiabing]

![Uploading 截屏2024-02-26 10.26.50.png…]()

[mvadari]

That's an amendment, not an actual breaking change. All amendments are technically breaking changes, but rarely change APIs.