Tags: denyeart/fabric-protos
Tags
Tag NPM packages from main branch as either next or next-unstable Pushed commits to the main branch published NPM packages tagged as `unstable`, and release tags on the main branch published NPM packaged tagged as `latest`. This conflicted with NPM packages published from the 0.2.x branch and meant that the target Fabric version for the NPM package currently tagged `latest` varied depending on which branch had a release created most recently. The `latest` tag should always correspond to the current Fabric LTS release since it is the default version installed if a specific version is not specified. Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
Update dependencies to address CVE-2023-2976 Signed-off-by: Mark S. Lewis <Mark.S.Lewis@outlook.com>
Bump version to 0.1.4 (hyperledger#116) Signed-off-by: James Taylor <jamest@uk.ibm.com>
Update Java binding build (hyperledger#114) Fix errors and warnings from maven publish, i.e. ``` Repository "orghyperledger-1045" failures Rule "sources-staging" failures * Missing: no sources jar found in folder '/org/hyperledger/fabric/fabric-protos/0.1.2' Rule "javadoc-staging" failures * Missing: no javadoc jar found in folder '/org/hyperledger/fabric/fabric-protos/0.1.2' ``` and ``` 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-gpg-plugin is missing. ``` Signed-off-by: James Taylor <jamest@uk.ibm.com>
PreviousNext