Releases: hyperledger/fabric-chaincode-node
v2.2.0 Node Chaincode - LTS
Release Notes
The v2.2.0 release is the LTS version of the fabric-chaincode-node
Fabric Chaincode Node v2.1.4
v2.1.4
Release Notes
-
FABCN-418 Dependency unable to use git
Locks the version of the winston library to 3.2.1
The updated winston library after 3.3.0 prevents chaincode installing due to
a new requirement for git which is not available in the
hyperledger/fabric-nodeenv docker image.
The release-2.0 branch has been renamed to release-2.x; the v2.1.0 release supercedes v2.0.0.
The release-1.4 branch is currently LTS, please see the proposed Fabric LTS strategy for more information:
hyperledger/fabric-rfcs#23
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-2.x/CHANGELOG.md#v2.1.4
Fabric Chaincode v2.1.3
v2.1.3
Release Notes
Locks the version of the @grpc/grpc-js library to 1.0.3
The updated grpc lirbary of 1.1.0 prevents the chaincode from contacting the peer.
The release-2.0 branch has been renamed to release-2.x; the v2.1.0 release supercedes v2.0.0.
The release-1.4 branch is currently LTS, please see the proposed Fabric LTS strategy for more information:
hyperledger/fabric-rfcs#23
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-2.x/CHANGELOG.md#v2.1.3
Fabric Chaincode Node v2.1.2
v2.1.2
Release Notes
This release fixes a bug when querying more than 100 assets.
The release-2.0 branch has been renamed to release-2.x; the v2.1.0 release supercedes v2.0.0.
The release-1.4 branch is currently LTS, please see the proposed Fabric LTS strategy for more information:
hyperledger/fabric-rfcs#23
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-2.x/CHANGELOG.md#v2.1.2
Fabric Chaincode Node v2.1.1
v2.1.1
Release Notes
There are minimal changes between v2.1.0 and v2.1.1, please see the change log for a full list of updates.
The release-2.0 branch has been renamed to release-2.x; the v2.1.0 release supersedes v2.0.0.
The release-1.4 branch is currently LTS, please see the proposed Fabric LTS strategy for more information:
hyperledger/fabric-rfcs#23
- FABCN-394 fabric-shim incorrectly implements interface ChaincodeStub from fabric-shim-api
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-2.x/CHANGELOG.md#v2.1.1
v2.1.0
v2.1.0
Release Notes
There are minimal changes between v2.0.0 and v2.1.0, please see the change log for a full list of updates.
The release-2.0 branch has been renamed to release-2.x; the v2.1.0 release supercedes v2.0.0.
The release-1.4 branch is currently LTS, please see the proposed Fabric LTS strategy for more information:
hyperledger/fabric-rfcs#23
- FABCN-373 Added a compatibility.md file, explaining support for node and fabric versions
- FABCN-381 Exposes a new shim function for returning the CORE_PEER_LOCALMSPID peer environment variable
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-2.x/CHANGELOG.md#v2.1.0
Fabric Chaincode Node v1.4.5
v1.4.5 5th February 2020
Release Notes
This is a maintenance release and contains bug fixes and minor updates.
-
The version of the x509 library has been updated so the library can now
be built with NodeJS v12 -
The checks on the number of parameters passed to a Java Script contract are
enforced -
previously the npm modules were shrinkwrapped; with the devDependencies
this has been changed so the final module size is smallerNote that contract and chaincode implementations are strongly advised to
shrinkwrap their own code
Migration Notes
None known
Known Vulnerabilities
none
Resolved Vulnerabilities
none
Known Issues & Workarounds
none
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-1.4/CHANGELOG.md#v145
v2.0.0
v2.0.0, 22 January 2020
Release Notes
The main change in the v2.0.0 is the level of NodeJS runtime has moved up to the latest LTS version of v12.13.0
v2.0.0 has the fixes from v1.4.4 level.
Migration Notes
Note that a change needed to be made to the metadata schema as it was in error; it had diverged from the JSONSchema standard
so that it was not possible to validate complex objects.
If you have custom metadata defined in the contract, then for the complex objects defined in the 'components' section
the properties of this object where previously held as array; they now need to be held as a map with the key as the name
of the property
Return types on functions where returned as an array of schema objects. this has been modified to be a single object. i.e.
the single value array is now just a single value.
There is also a new nodeenv docker image that is used for hosting the chaincode rather than use the baseos image as in V1.4
In v1.4, the fabric-contract-api had a dependency on the fabric-shim. This has changed in this version to have a dependency
on the new fabric-shim-api module. This allows the fabric-contract-api to be used client side for annotations.
For contributors, the v2.0.0 repo is built using rush and is organized as a full mono-repo.
The @object annotation has been deprecated in favour of the @datatype annotation
The x509 library used for parsing has changed; this should be parse the X509 certificates exactly the same way; this is a note that
differences are observed in the parsed certificates please raise an issue.
Summary of the programming model
This is designed to improve developer productivity and ease of use.
For more information see https://hyperledger-fabric.readthedocs.io/en/developapps/developing_applications.html
Known Vulnerabilities
none
Resolved Vulnerabilities
none
Known Issues & Workarounds
none
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-2.0/CHANGELOG.md#v2.0.0
v2.0.0-beta
v2.0.0-beta, 12 December 2019
Release Notes
The main change in the v2.0.0 beta is the level of NodeJS runtime has moved up to the latest LTS version of v12.13.0
v2.0.0 beta has the fixes from v1.4.4 level.
Migration Notes
Note that a change needed to be made to the metadata schema as it was in error; it had diverged from the JSONSchema standard
so that it was not possible to validate complex objects.
If you have custom metadata defined in the contract, then for the complex objects defined in the 'components' section
the properties of this object where previously held as array; they now need to be held as a map with the key as the name
of the property
Return types on functions where returned as an array of schema objects. this has been modified to be a single object. i.e.
the single value array is now just a single value.
There is also a new nodeenv docker image that is used for hosting the chaincode rather than use the baseos image as in V1.4
In v1.4, the fabric-contract-api had a dependency on the fabric-shim. This has changed in this version to have a dependency
on the new fabric-shim-api module. This allows the fabric-contract-api to be used client side for annotations.
For contributors, the v2.0.0 repo is built using rush and is organized as a full mono-repo.
The @object annotation has been deprecated in favour of the @datatype annotation
The x509 library used for parsing has changed; this should be parse the X509 certificates exactly the same way; this is a note that
differences are observed in the parsed certificates please raise an issue.
Summary of the programming model
This is designed to improve developer productivity and ease of use.
For more information see https://hyperledger-fabric.readthedocs.io/en/developapps/developing_applications.html
Known Vulnerabilities
none
Resolved Vulnerabilities
none
Known Issues & Workarounds
none
Change Log
v1.4.4: Set npmjs registry
v1.4.4 12 November, 2019
This is a re-release of v1.4.4; with a CI pipeline change, there are some 'teething issues' we're working through.
Release Notes
This is a maintence release and contains bug fixes, and minor updates.
Migration Notes
None known
Known Vulnerabilities
none
Resolved Vulnerabilities
none
Known Issues & Workarounds
none
Change Log
https://github.com/hyperledger/fabric-chaincode-node/blob/release-1.4/CHANGELOG.md#v144