Tags: ernestwisniewski/cardano-node
Tags
Merge IntersectMBO#2671 2671: Prepare 1.27.0 release. r=nc6 a=nc6 Co-authored-by: Nicholas Clarke <nick@topos.org.uk> Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io> Co-authored-by: Nicholas Clarke <nicholas.clarke@iohk.io>
Merge IntersectMBO#2487 2487: Release 1.26.0 r=nc6 a=nc6 Changelogs and versions updated. Co-authored-by: Nicholas Clarke <nick@topos.org.uk>
Merge IntersectMBO#2296 2296: Last dep update for 1.25.0 r=dcoutts a=dcoutts The final things in consensus and ledger libs. TODO: * [x] bump versions * [ ] update change logs Co-authored-by: Duncan Coutts <duncan@well-typed.com>
Merge IntersectMBO#2194 2194: Bump version to 1.24.2 and update change logs r=intricate a=dcoutts A few small fixes and improvements in the node and cli since 1.24.1 for issues found during integration testing. Co-authored-by: Duncan Coutts <duncan@well-typed.com>
Merge IntersectMBO#2181 2181: Release 1.24.1 r=johnalotoski a=dcoutts Bump dependency on ledger lib to bring in a fix for the serialisation for mutli-asset values: accept the full 64-bit range for quantities. Update the change logs for recent fixes. Co-authored-by: Duncan Coutts <duncan@well-typed.com>
Merge IntersectMBO#2154 2154: Classify an empty Value as consisting of 0 Lovelace r=dcoutts a=dcoutts The valueToLovelace check if the value consists of only Lovelace and no other assets, and if so then return the Lovelace. Previously this function classified an empty value as not consisting of only Lovelace. It is more useful to classify it the other way around and define the result to be Just 0. In particular this valueToLovelace check is used to see if a tx out is using the multi-asset syntax, and when parsed as a multi-asset value "0" is classified (correctly) as empty, since we do not represent 0 quantities. It's more useful to define this case as not using multi-asset and to say this does consist only of Lovelace, with quantity zero. Co-authored-by: Duncan Coutts <duncan@well-typed.com>
PreviousNext