Composer v0.20.5

Welcome to Hyperledger Composer v0.20.5, which comes with some logging and bug fixes, to help keep you all Composing. Also we can confirm the Composer v0.20 can be used with hyperledger fabric 1.3.0. It doesn't exploit any features of this release but does tolerate it.

Bug fixes

🐞 #4532 Fixes an issue where a websocket client can terminate the rest server 🐞 #4536 Fixes the logging of transaction ids for the performance (verbose) logging in chaincode 🐞 #4539 Corrects the cloud wallets documentation 🐞 #4542 Removes old information from the rest server readme as seen on npm 🐞 #4523 Minor improvements to chaincode logging 🐞 #4525 Clarify node versions in documentation (Thanks to @doowb ) 🐞 #4529 Fabric client initialize channel always uses the first peer (Thanks to @volodyad )

Notes

⚠️ If using the Composer tooling to create a Hyperledger Fabric development server, this will now be creating a v1.2.1 server by default. If you are using a different level of Composer v0.16.x, you will need to set the relevant environment variable via export FABRIC_VERSION=hlfvXX when using the Hyperledger Fabric development servers provided by Composer:

• hlfv1 for Fabric v1.0
• hlfv11 for Fabric v1.1
• hlfv12 for Fabric v1.2

⚠️ There are multiple support splits across differing Fabric levels, so please be careful with what versions are being used:

• v0.20.0 and above are compatible with the Fabric 1.2.0, 1.2.1 and 1.3.0 driver only
• v0.18.2, v0.19.0 and above are compatible with the Fabric 1.1.0 driver only
• v0.18.0 -> v0.18.1 are compatible with the Fabric RC1 driver only
• v0.17.3 -> v0.17.6 are compatible with Fabric alpha driver only
• v0.17.0 -> v0.17.2 are compatible with Fabric preview driver only

⚠️ The is a change in the business network lifecycle administration, and business network card commands between v0.18.2 and v0.19.0