Import 1.34 changelogs from release branch.

IntersectMBO · May 23, 2022 · 82067b7 · 82067b7
1 parent d0b0fa1
commit 82067b7
Show file tree

Hide file tree

Showing 3 changed files with 138 additions and 0 deletions.
diff --git a/cardano-api/ChangeLog.md b/cardano-api/ChangeLog.md
@@ -1,5 +1,19 @@
 # Changelog for cardano-api
 
+## 1.34.0 -- February 2022
+
+- Expose `lovelaceToTxOutValue`. (#3381)
+- Implement two functions: `currentEpochEligibleLeadershipSlots` and
+  `nextEpochEligibleLeadershipSlots` to get the leadership slots for the
+  current/next epoch respectively. (#3464, #3494)
+- Various small intenral fixes. (#3466)
+- Add a `capi` library to support using the cardano node as a C library in other
+  software. (#3501)
+- `fromShelleyAddr` now takes an explicit `ShelleyBasedEra` parameter to
+  determine the era. The previous behaviour (with an implicit
+  `IsShelleyBasedEra` constraint) can be obtained with `fromShelleyAddrIsSbe`.
+  (#2253, #3606)
+
 ## 1.33.0 -- December 2021
 ## 1.32.1 -- November 2021
 

diff --git a/cardano-cli/ChangeLog.md b/cardano-cli/ChangeLog.md
@@ -1,5 +1,91 @@
 # Changelog for cardano-cli
 
+## 1.34.0 -- February 2022
+
+- Fix some spelling errors in the CLI help text.  (#3499)
+- Add a prettier rendering of update proposals. (#3208)
+- Add support for CBOR-encoded blobs in the `transaction build` and `transaction
+  build-raw` commands. (#3483)
+- Implement a `leadership-schedule` command. This can calculate a stake pool's
+  leadership schedule for the current and following epoch. It requires access to
+  the VRF signing key for that stake pool.
+
+  ```
+  > cardano-cli query leadership-schedule \
+     --testnet-magic 42 \
+     --genesis example/shelley/genesis.json \
+     --stake-pool-id  pool12t0y7agkqct89pf00eeytkvfjlquv76tjy27duannan9w63ckxv \
+     --vrf-signing-key-file example/node-pool1/shelley/vrf.skey
+     --current
+     SlotNo                          UTC Time
+     --------------------------------------------------------
+     4073                   2021-12-29 17:26:54.998001755 UTC
+     4126                   2021-12-29 17:27:00.298001755 UTC
+     4206                   2021-12-29 17:27:08.298001755 UTC
+     4256                   2021-12-29 17:27:13.298001755 UTC
+     4309                   2021-12-29 17:27:18.598001755 UTC
+     4376                   2021-12-29 17:27:25.298001755 UTC
+     4423                   2021-12-29 17:27:29.998001755 UTC
+     4433                   2021-12-29 17:27:30.998001755 UTC
+  ``` (#3464, #3494)
+- The CLI now supports outputting transaction bodies in ledger-compliant CDDL in
+  the `transaction build` and `transaction build-raw` commands. This is
+  specified by using the `--cddl-format` flag. (#3505)
+- Implement a `kes-period-info` command in the CLI. This checks that your
+  operational certificate is correct. It checks:
+  - The counters match what is in the node's protocol state
+  - The KES period in the operational certificate is correct (based on the
+    current slot).
+  ```
+  > cardano-cli query kes-period-info --testnet-magic 42  \
+    --op-cert-file example/node-pool1/shelley/node.cert
+  ✓ The operational certificate counter agrees with the node protocol state counter
+  ✓ Operational certificate's kes period is within the correct KES period interval
+  {
+      "qKesNodeStateOperationalCertificateNumber": 6,
+      "qKesCurrentKesPeriod": 404,
+      "qKesOnDiskOperationalCertificateNumber": 6,
+      "qKesRemainingSlotsInKesPeriod": 3760228,
+      "qKesMaxKESEvolutions": 62,
+      "qKesKesKeyExpiry": "2022-03-20T21:44:51Z",
+      "qKesEndKesInterval": 434,
+      "qKesStartKesInterval": 372,
+      "qKesSlotsPerKesPeriod": 129600
+  }
+  ``` (#3459, #3572, #3599)
+- The CLI now displays collateral inputs in a nicer fashion. (#3463)
+- The `transaction sign` command now allows for incremental signing by providing
+  an already signed transaction via `--tx-file`. This allows more easily adding
+  multiple signatures to a transaction. (#3549)
+- The `transaction build` command now supports an option
+  (`--calculate-plutus-script-cost`) to compute the cost for included scripts.
+  ```
+  cardano-cli transaction build \
+  --alonzo-era \
+  --cardano-mode \
+  --testnet-magic "$TESTNET_MAGIC" \
+  --change-address "$utxoaddr" \
+  --tx-in "$plutusutxotxin" \
+  --tx-in-collateral "$txinCollateral" \
+  --tx-out "$dummyaddress+10000000" \
+  --tx-in-script-file "$plutusscriptinuse" \
+  --tx-in-datum-file "$datumfilepath"  \
+  --protocol-params-file "$WORK/pparams.json" \
+  --tx-in-redeemer-file "$redeemerfilepath" \
+  --calculate-plutus-script-cost "$WORK/create-datum-output.scriptcost"
+  > cat $WORK/create-datum-output.scriptcost
+  [
+    {
+        "executionUnits": {
+            "memory": 1700,
+            "steps": 476468
+        },
+        "lovelaceCost": 133,
+        "scriptHash": "67f33146617a5e61936081db3b2117cbf59bd2123748f58ac9678656"
+    }
+  ]
+  ``` (#3589)
+
 ## 1.33.0 -- December 2021
 ## 1.32.1 -- November 2021
 

diff --git a/cardano-node/ChangeLog.md b/cardano-node/ChangeLog.md
@@ -1,5 +1,43 @@
 # Changelog for cardano-node
 
+## 1.34.1 -- March 2022
+
+### node changes
+- Fix tracer config mismatches #3668
+- Fix #3664: Restore legacy metrics #3676
+
+## 1.34.0 -- February 2022
+
+### node changes
+
+- Separate the logic for shutdown via IPC and shutdown on reaching a specified
+  slot. (#3320, #3508)
+- Tests for certifying and withdrawing Plutus scripts. (#3318)
+- Improvements to the `tx-generator` internal testing infrastructure. (#3448)
+- Various documentation updates. (#2875, #2884, #2839, #2904, #3476, #3482,
+  #3486, #3500, #3502, #3542, #3553, #3573, #3603)
+- Integrate the new tracing system in `cardano-node`. (#3450, #3496, #3497,
+  #3498, #3570)
+- The stake credential history tool now additionally displays the protocol
+  version. (#3409)
+
+### network changes
+
+- Add a new mini-protocol to query the local mempool. (#3404)
+- Additional testing coverage. (#3517)
+- Stop the MUX in case of miniprotocol timeout. This can happen if a peer is
+  demoted to cold, and could result in lingering miniprotocols in an unknown
+  state if the peer is again promoted. (#3575, #3580)
+- Avoid ordering peers based upon peerid in block fetch. Ordering based on
+  peerid would often result in all nodes choosing the same second, third choice
+  peers etc. These are now based on a node-local random ordering. (#3535)
+- Fix a spurious assertion failure that could be seen with regards to demoted
+  hot peers. (#3588)
+
+### consensus changes
+
+- Various internal improvements. (#3557, #3560)
+
 ## 1.33.0 -- December 2021
 
 ### node changes