Release notes
LedgerGraph is a standalone service that operates on a different release cadence to the Corda platform.
The following table shows the compatibility of the LedgerGraph service versions with Corda Enterprise:
LedgerGraph version | Corda Enterprise version | JDK version |
---|---|---|
1.2.x | 4.11.x and below | JDK 8 |
1.3.x | 4.12.x | JDK 17 |
LedgerGraph 1.3 release notes
LedgerGraph 1.3 is a major release supporting Java 17 and Kotlin 1.9.20. If you want to use LedgerGraph, this is the only release that works with Corda 4.12.
LedgerGraph 1.2.5 release notes
In this release:
- It is now possible to enable
inboundReferencesOnly
when checking if a DAG object is related to any other DAG that is unconsumed using theisRelatedToUnconsumedDAG
method. This ignores DAGs that have an outbound reference to an unconsumed DAG.
LedgerGraph 1.2.4 release notes
In this release:
- A configuration option has been added which allows LedgerGraph to handle transactions that cause failures during initialization. For more information, see the LedgerGraph documentation.
LedgerGraph 1.2.3 release notes
In this release:
- Logging of the Archiving tool has been increased to aid in troubleshooting.
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.