github.com/darrenli6/fabric-sdk-example@v0.0.0-20220109053535-94b13b56df8c/docs/source/releases.rst (about) 1 Release Notes 2 ============= 3 4 `v1.0.6 <https://github.com/hyperledger/fabric/releases/tag/v1.0.6>`__ 5 February 18, 2018 6 7 Bug fixes, documentation and test coverage improvements, UX improvements 8 based on user feedback and changes to address a variety of static scan 9 findings (unused code, static security scanning, spelling, linting and more). 10 11 Known Vulnerabilities 12 none 13 14 Resolved Vulnerabilities 15 none 16 17 Known Issues & Workarounds 18 The fabric-ccenv image which is used to build chaincode, currently includes 19 the github.com/hyperledger/fabric/core/chaincode/shim ("shim") package. 20 This is convenient, as it provides the ability to package chaincode 21 without the need to include the "shim". However, this may cause issues in future 22 releases (and/or when trying to use packages which are included by the "shim"). 23 24 In order to avoid any issues, users are advised to manually vendor the "shim" 25 package with their chaincode prior to using the peer CLI for packaging and/or 26 for installing chaincode. 27 28 Please refer to https://jira.hyperledger.org/browse/FAB-5177 for more details, 29 and kindly be aware that given the above, we may end up changing the 30 fabric-ccenv in the future. 31 32 `Change Log <https://github.com/hyperledger/fabric/blob/v1.0.6/CHANGELOG.md#v106>`__ 33 34 `v1.0.5 <https://github.com/hyperledger/fabric/releases/tag/v1.0.5>`__ 35 December 4, 2017 36 37 Bug fixes, documentation and test coverage improvements, UX improvements 38 based on user feedback and changes to address a variety of static scan 39 findings (unused code, static security scanning, spelling, linting and more). 40 41 Known Vulnerabilities 42 none 43 44 Resolved Vulnerabilities 45 none 46 47 Known Issues & Workarounds 48 The fabric-ccenv image which is used to build chaincode, currently includes 49 the github.com/hyperledger/fabric/core/chaincode/shim ("shim") package. 50 This is convenient, as it provides the ability to package chaincode 51 without the need to include the "shim". However, this may cause issues in future 52 releases (and/or when trying to use packages which are included by the "shim"). 53 54 In order to avoid any issues, users are advised to manually vendor the "shim" 55 package with their chaincode prior to using the peer CLI for packaging and/or 56 for installing chaincode. 57 58 Please refer to https://jira.hyperledger.org/browse/FAB-5177 for more details, 59 and kindly be aware that given the above, we may end up changing the 60 fabric-ccenv in the future. 61 62 `Change Log <https://github.com/hyperledger/fabric/blob/v1.0.5/CHANGELOG.md#v105>`__ 63 64 `v1.0.4 <https://github.com/hyperledger/fabric/releases/tag/v1.0.4>`__ 65 October 31, 2017 66 67 Bug fixes, documentation and test coverage improvements, UX improvements 68 based on user feedback and changes to address a variety of static scan 69 findings (unused code, static security scanning, spelling, linting and more). 70 71 Known Vulnerabilities 72 none 73 74 Resolved Vulnerabilities 75 none 76 77 Known Issues & Workarounds 78 The fabric-ccenv image which is used to build chaincode, currently includes 79 the github.com/hyperledger/fabric/core/chaincode/shim ("shim") package. 80 This is convenient, as it provides the ability to package chaincode 81 without the need to include the "shim". However, this may cause issues in future 82 releases (and/or when trying to use packages which are included by the "shim"). 83 84 In order to avoid any issues, users are advised to manually vendor the "shim" 85 package with their chaincode prior to using the peer CLI for packaging and/or 86 for installing chaincode. 87 88 Please refer to https://jira.hyperledger.org/browse/FAB-5177 for more details, 89 and kindly be aware that given the above, we may end up changing the 90 fabric-ccenv in the future. 91 92 `Change Log <https://github.com/hyperledger/fabric/blob/v1.0.4/CHANGELOG.md#v104>`__ 93 94 `v1.0.3 <https://github.com/hyperledger/fabric/releases/tag/v1.0.3>`__ 95 October 3, 2017 96 97 Bug fixes, documentation and test coverage improvements, UX improvements 98 based on user feedback and changes to address a variety of static scan 99 findings (unused code, static security scanning, spelling, linting and more). 100 101 Known Vulnerabilities 102 none 103 104 Resolved Vulnerabilities 105 none 106 107 Known Issues & Workarounds 108 The fabric-ccenv image which is used to build chaincode, currently includes 109 the github.com/hyperledger/fabric/core/chaincode/shim ("shim") package. 110 This is convenient, as it provides the ability to package chaincode 111 without the need to include the "shim". However, this may cause issues in future 112 releases (and/or when trying to use packages which are included by the "shim"). 113 114 In order to avoid any issues, users are advised to manually vendor the "shim" 115 package with their chaincode prior to using the peer CLI for packaging and/or 116 for installing chaincode. 117 118 Please refer to https://jira.hyperledger.org/browse/FAB-5177 for more details, 119 and kindly be aware that given the above, we may end up changing the 120 fabric-ccenv in the future. 121 122 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v103>`__ 123 124 `v1.0.2 <https://github.com/hyperledger/fabric/releases/tag/v1.0.2>`__ 125 August 31, 2017 126 127 Bug fixes, documentation and test coverage improvements, UX improvements 128 based on user feedback and changes to address a variety of static scan 129 findings (unused code, static security scanning, spelling, linting and more). 130 131 Known Vulnerabilities 132 none 133 134 Resolved Vulnerabilities 135 https://jira.hyperledger.org/browse/FAB-5753 136 https://jira.hyperledger.org/browse/FAB-5899 137 138 Known Issues & Workarounds 139 The fabric-ccenv image which is used to build chaincode, currently includes 140 the github.com/hyperledger/fabric/core/chaincode/shim ("shim") package. 141 This is convenient, as it provides the ability to package chaincode 142 without the need to include the "shim". However, this may cause issues in future 143 releases (and/or when trying to use packages which are included by the "shim"). 144 145 In order to avoid any issues, users are advised to manually vendor the "shim" 146 package with their chaincode prior to using the peer CLI for packaging and/or 147 for installing chaincode. 148 149 Please refer to https://jira.hyperledger.org/browse/FAB-5177 for more details, 150 and kindly be aware that given the above, we may end up changing the 151 fabric-ccenv in the future. 152 153 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v102>`__ 154 155 `v1.0.1 <https://github.com/hyperledger/fabric/releases/tag/v1.0.1>`__ 156 August 5, 2017 157 158 Bug fixes, documentation and test coverage improvements, UX improvements 159 based on user feedback and changes to address a variety of static scan 160 findings (unused code, static security scanning, spelling, linting and more). 161 162 Known Vulnerabilities 163 none 164 165 Resolved Vulnerabilities 166 https://jira.hyperledger.org/browse/FAB-5329 167 https://jira.hyperledger.org/browse/FAB-5330 168 https://jira.hyperledger.org/browse/FAB-5353 169 https://jira.hyperledger.org/browse/FAB-5529 170 https://jira.hyperledger.org/browse/FAB-5606 171 https://jira.hyperledger.org/browse/FAB-5627 172 173 Known Issues & Workarounds 174 The fabric-ccenv image which is used to build chaincode, currently includes 175 the github.com/hyperledger/fabric/core/chaincode/shim ("shim") package. 176 This is convenient, as it provides the ability to package chaincode 177 without the need to include the "shim". However, this may cause issues in future 178 releases (and/or when trying to use packages which are included by the "shim"). 179 180 In order to avoid any issues, users are advised to manually vendor the "shim" 181 package with their chaincode prior to using the peer CLI for packaging and/or 182 for installing chaincode. 183 184 Please refer to https://jira.hyperledger.org/browse/FAB-5177 for more details, 185 and kindly be aware that given the above, we may end up changing the 186 fabric-ccenv in the future. 187 188 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v101>`__ 189 190 `v1.0.0 <https://github.com/hyperledger/fabric/releases/tag/v1.0.0>`__ 191 July 11, 2017 192 193 Bug fixes, documentation and test coverage improvements, UX improvements 194 based on user feedback and changes to address a variety of static scan 195 findings (removal of unused code, static security scanning, spelling, linting 196 and more). 197 198 Known Vulnerabilities 199 none 200 201 Resolved Vulnerabilities 202 https://jira.hyperledger.org/browse/FAB-5207 203 204 Known Issues & Workarounds 205 The fabric-ccenv image which is used to build chaincode, currently includes 206 the github.com/hyperledger/fabric/core/chaincode/shim ("shim") package. 207 This is convenient, as it provides the ability to package chaincode 208 without the need to include the "shim". However, this may cause issues in future 209 releases (and/or when trying to use packages which are included by the "shim"). 210 211 In order to avoid any issues, users are advised to manually vendor the "shim" 212 package with their chaincode prior to using the peer CLI for packaging and/or 213 for installing chaincode. 214 215 Please refer to https://jira.hyperledger.org/browse/FAB-5177 for more details, 216 and kindly be aware that given the above, we may end up changing the 217 fabric-ccenv in the future. 218 219 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v100>`__ 220 221 `v1.0.0-rc1 <https://github.com/hyperledger/fabric/releases/tag/v1.0.0-rc1>`__ 222 June 23, 2017 223 224 Bug fixes, documentation and test coverage improvements, UX improvements 225 based on user feedback and changes to address a variety of static scan 226 findings (unused code, static security scanning, spelling, linting and more). 227 228 Known Vulnerabilities 229 none 230 231 Resolved Vulnerabilities 232 https://jira.hyperledger.org/browse/FAB-4856 233 https://jira.hyperledger.org/browse/FAB-4848 234 https://jira.hyperledger.org/browse/FAB-4751 235 https://jira.hyperledger.org/browse/FAB-4626 236 https://jira.hyperledger.org/browse/FAB-4567 237 https://jira.hyperledger.org/browse/FAB-3715 238 239 Known Issues & Workarounds 240 none 241 242 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v100-rc1>`__ 243 244 `v1.0.0-beta <https://github.com/hyperledger/fabric/releases/tag/v1.0.0-beta>`__ 245 June 8, 2017 246 247 Bug fixes, documentation and test coverage improvements, UX improvements based 248 on user feedback and changes to address a variety of static scan findings (unused 249 code, static security scanning, spelling, linting and more). 250 251 Upgraded to `latest version <https://github.com/grpc/grpc-go/releases/>`__ (a 252 precursor to 1.4.0) of gRPC-go and implemented keep-alive feature for improved 253 resiliency. 254 255 Added a `new tool <https://github.com/hyperledger/fabric/tree/master/examples/configtxupdate>`__ 256 `configtxlator` to enable users to translate the contents of a channel configuration transaction 257 into a human readable form. 258 259 Known Vulnerabilities 260 261 none 262 263 Resolved Vulnerabilities 264 265 none 266 267 Known Issues & Workarounds 268 269 BCCSP content in the configtx.yaml has been `removed <https://github.com/hyperledger/fabric/commit/a997c30>`__. This change will cause a panic when running `configtxgen` tool with a configtx.yaml file that includes the removed BCCSP content. 270 271 Java Chaincode support has been disabled until post 1.0.0 as it is not yet fully mature. It may be re-enabled for experimentation by cloning the hyperledger/fabric repository, reversing `this commit <https://github.com/hyperledger/fabric/commit/29e0c40>`__ and building your own fork. 272 273 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v100-beta>`__ 274 275 `v1.0.0-alpha2 <https://github.com/hyperledger/fabric/releases/tag/v1.0.0-alpha2>`__ 276 277 The second alpha release of the v1.0.0 Hyperledger Fabric. The code is 278 now feature complete. From now until the v1.0.0 release, the community is 279 focused on documentation improvements, testing, hardening, bug fixing and 280 tooling. We will be releasing successive release candidates periodically as 281 the release firms up. 282 283 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v100-alpha2-may-15-2017>`__ 284 285 `v1.0.0-alpha <https://github.com/hyperledger/fabric/releases/tag/v1.0.0-alpha>`__ 286 March 16, 2017 287 288 The first alpha release of the v1.0.0 Hyperledger Fabric. The code is 289 being made available to developers to begin exploring the v1.0 architecture. 290 291 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v100-alpha-march-16-2017>`__ 292 293 `v0.6-preview <https://github.com/hyperledger/fabric/tree/v0.6>`__ 294 September 16, 2016 295 296 A developer preview release of the Hyperledger Fabric intended to 297 exercise the release logistics and stabilize a set of capabilities for 298 developers to try out. This will be the last release under the original 299 architecture. All subsequent releases will deliver on the v1.0 300 architecture. 301 302 `Change Log <https://github.com/hyperledger/fabric/blob/master/CHANGELOG.md#v06-preview-september-16-2016>`__ 303 304 `v0.5-developer-preview <https://github.com/hyperledger-archives/fabric/tree/v0.5-developer-preview>`__ 305 June 17, 2016 306 307 A developer preview release of the Hyperledger Fabric intended to 308 exercise the release logistics and stabilize a set of capabilities for 309 developers to try out. 310 311 Key features: 312 313 Permissioned blockchain with immediate finality Chaincode (aka smart 314 contract) execution environments Docker container (user chaincode) 315 In-process with peer (system chaincode) Pluggable consensus with PBFT, 316 NOOPS (development mode), SIEVE (prototype) Event framework supports 317 pre-defined and custom events Client SDK (Node.js), basic REST APIs and 318 CLIs Known Key Bugs and work in progress 319 320 - 1895 - Client SDK interfaces may crash if wrong parameter specified 321 - 1901 - Slow response after a few hours of stress testing 322 - 1911 - Missing peer event listener on the client SDK 323 - 889 - The attributes in the TCert are not encrypted. This work is 324 still on-going 325 326 .. Licensed under Creative Commons Attribution 4.0 International License 327 https://creativecommons.org/licenses/by/4.0/