Skip to content

Commit

Permalink
Node 16 and v1.4 libraries (#3357)
Browse files Browse the repository at this point in the history
Clarify notes on the v1.4 Chaincode with Node16

Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
(cherry picked from commit f30d3cd)
  • Loading branch information
mbwhite authored and denyeart committed Apr 26, 2022
1 parent f6e8336 commit 1c97ab1
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions docs/source/upgrade_to_newest_version.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,13 @@ Support for user chaincodes to utilize the chaincode shim's logger via `NewLogge

For more information, check out [Logging control](./logging-control.html#chaincode).

#### Nodejs v1.4 Chaincode

For v1.4 Nodejs chaincode libraries, the supported node runtime is v8. Though not formally supported, the v1.4 libraries can work on later versions. For example the Node12 runtime that was used with Fabric v2.2. Fabric v2.4 has upgraded to Node16. It is _not possible_ to run the v1.4 libraries on Node 16. Therefore any chaincode written with the v1.4 libraries will need to be updated. Typically this will be before upgrading to a Fabric 2.4 peer.

Also please note that the v1.4 libraries themselves are not supported, and will no longer get updates. Please migrate to a v2 Node chaincode library.

For detailed information please refer to the [compatibility](https://github.com/hyperledger/fabric-chaincode-node/blob/main/COMPATIBILITY.md) document in the `fabric-chaincode-node` repository.
### While upgrading peer nodes

#### Peer databases upgrade
Expand Down

0 comments on commit 1c97ab1

Please sign in to comment.